MCP Atlassian Server

confluence_get_page

Retrieve a Confluence page by its ID. Optionally expand properties like body.storage or version for detailed content.

Instructions

Get a specific Confluence page by ID

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pageId": "<pageId>"
    },
    "name": "confluence_get_page"
  }
}

Input Schema

Name	Required	Description	Default
`expand`	No	Comma-separated list of properties to expand (e.g., "body.storage,version")
`pageId`	Yes	The ID of the page to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 18, 2026

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry the full behavioral burden. It only indicates a read operation ('Get') but does not disclose error behavior (e.g., if pageId is invalid), rate limits, authentication needs, or whether the response includes full content or just metadata. The existence of the expand parameter is not hinted at in the description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, focused sentence. It earns its place by stating the core purpose, but it could include more detail without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with full schema coverage, the description is adequate but has gaps: it lacks explanation of return values (since no output schema is provided) and does not differentiate from sibling tools or mention the expand parameter's role in controlling the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The input schema already documents both parameters (pageId required, expand optional with an example). The description adds no extra meaning or usage context for the parameters beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Get a specific Confluence page by ID', specifying the verb (get) and resource (Confluence page) with the method (by ID). It implicitly distinguishes from sibling tools like confluence_search and confluence_create_page, but does not explicitly elaborate on what is returned (e.g., full content) or scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no guidance on when to use this tool versus alternatives like confluence_search (for finding pages) or confluence_get_spaces (for a different resource). It does not mention prerequisites, context, or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server