Fetch detailed information about a specific content item using its ID and workspace ID. Resolves access context with optional hub profile.
Get content item details by ID (v1 schema).
workspace_id: target workspace ID — get available IDs from list_workspaces()
hub_profile_id: optional, used to resolve access context
| Name | Required | Description | Default |
|---|---|---|---|
| content_id | Yes | ||
| workspace_id | Yes | ||
| hub_profile_id | No |
Changes observed during successful MCP inspections.
v0.4.18Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly and non-destructive behavior. The description adds no further behavioral details (e.g., error conditions, partial responses) and does not contradict the annotations. Credit given for consistency, but no extra insight.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise, with no redundant words or irrelevant details. It gets straight to the point and includes the necessary version qualifier.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema or return format is mentioned, and the description does not address how this tool differs from get_content_v2. Combined with the missing content_id description, the tool is under-specified for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description explains workspace_id and hub_profile_id, but fails to describe content_id, a required parameter. This is a significant omission that could lead to misuse. Schema coverage is incomplete.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves content item details by ID, and the '(v1 schema)' qualifier distinguishes it from get_content_v2. The verb and resource are specific.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus the sibling get_content_v2, nor any mention of the relationship between the two. An agent is left to infer selection criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.