jcm_getArticleFetch a Confluence page by numeric ID to get its title, markdown body, status, version, space, and parent details.
Fetch a Confluence page by ID. Returns {id, title, body (markdown), status, version, spaceId, parentId?}.
| Name | Required | Description | Default |
|---|---|---|---|
| pageId | Yes | Confluence page ID |
Changes observed during successful MCP inspections.
v0.10.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds useful return-shape context, including that body is markdown and parentId is optional, though it does not mention permissions or error behavior.
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?
Two short sentences, front-loaded with the core action and then the return fields. There is no redundant or wasted text.
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?
For a simple one-parameter read tool with full schema coverage and complete safety annotations, the description is complete enough. Even without an output schema, it briefly documents the returned structure.
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?
Schema description coverage is 100%, and the only parameter pageId is already documented as a Confluence page ID. The description adds no syntax or format detail beyond the schema baseline.
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 states a specific verb and resource: 'Fetch a Confluence page by ID.' It is clearly distinct from siblings such as jcm_searchArticles, jcm_createArticle, and jcm_updateArticle.
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?
The phrase 'by ID' implies the tool is for cases where a page ID is already known, but the description does not explicitly say when to use this instead of jcm_searchArticles or other retrieval tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.