Capacities API 2.0: MCP getObjectContent Returns Empty Responses

Hello Capacities Support Team,

I'm experiencing an issue with the Capacities API 2.0 integration through ChatGPT. After running several controlled diagnostic tests, I've isolated what appears to be a problem with the getObjectContent operation.

Issue summary

The getObjectContent command consistently returns an empty object ({}), even when the requested object exists and its content can be retrieved successfully through other API commands.

Environment

Integration: ChatGPT with the Capacities connector

API: Capacities API 2.0

Affected operation: getObjectContent

Object types tested: Books and Pages

Date tested: Oct. 17, 2026

Steps to reproduce

Locate an existing object using search or listObjectsByObjectType.

Confirm that the object exists and has a valid ID.

Call getObjectContent using that ID.

Observe that the response is {}.

Call readObjectBlocks using the same object ID.

Observe that the object's content blocks are returned successfully.

The same behavior occurs with newly created temporary pages.

Diagnostic results

Operation

Result

Search objects

Successful

List objects by type

Successful

Retrieve object type schema

Successful

Retrieve complete object content

Empty response ({})

Read object blocks

Successful

Create objects

Successful

Update object properties

Request accepted

Add and update content blocks

Successful and verified

Delete content blocks

Successful and verified

Delete temporary objects

Successful

10 sequential read requests

All successful

10 sequential write requests

All accepted

No rate-limit or authentication errors were encountered during these tests.

Business impact

I'm using the integration to maintain and enrich a substantial knowledge base containing books, people, movies, television shows and images.

Reliable retrieval of object properties and relationships is essential for these workflows. Without it, automated updates risk overwriting existing information or losing relationships.

This issue is preventing me from confidently resuming large-scale maintenance operations.

Questions

Is this a known issue with the current Capacities API 2.0 integration or MCP connector?

Is the empty response originating from the Capacities API or the connector's response-handling layer?

Is there a recommended workaround for retrieving complete object properties and relationships?

Are there any known restrictions or rate limits that could produce this behavior without returning an explicit error?

Is a fix planned, and is there an estimated timeline?

I can provide specific object IDs and additional diagnostic information if helpful.

Thank you for your assistance.