Skip to main content
Glama

confluence_get_page

Retrieve Confluence page content by ID or title and space key. Optionally include metadata and convert to markdown.

Instructions

Get content of a specific Confluence page by its ID, or by its title and space key.

Args: ctx: The FastMCP context. page_id: Confluence page ID. If provided, 'title' and 'space_key' are ignored. title: The exact title of the page. Must be used with 'space_key'. space_key: The key of the space. Must be used with 'title'. include_metadata: Whether to include page metadata. convert_to_markdown: Convert content to markdown (true) or keep raw HTML (false). sample: Return only top N lines or the whole page when set to -1.

Returns: JSON string representing the page content and/or metadata, or an error if not found or parameters are invalid.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoThe exact title of the Confluence page. Use this with 'space_key' if 'page_id' is not known.
sampleNoReturn only the first N lines of the page for inspection. Set to -1 for full page content.
page_idNoConfluence page ID (numeric ID, can be found in the page URL). For example, in the URL 'https://example.atlassian.net/wiki/spaces/TEAM/pages/123456789/Page+Title', the page ID is '123456789'. Provide this OR both 'title' and 'space_key'. If page_id is provided, title and space_key will be ignored.
space_keyNoThe key of the Confluence space where the page resides (e.g., 'DEV', 'TEAM'). Required if using 'title'.
include_metadataNoWhether to include page metadata such as creation date, last update, version, and labels.
convert_to_markdownNoWhether to convert page to markdown (true) or keep it in raw HTML format (false). Raw HTML can reveal macros (like dates) not visible in markdown, but CAUTION: using HTML significantly increases token usage in AI responses.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations exist, so description carries full burden. It discloses the two identification methods, the effect of include_metadata and convert_to_markdown, and warns about HTML token usage. Lacks mention of authorization or side effects, but as a read operation, this is sufficient.

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

Conciseness3/5

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

The description is adequately structured with Args and Returns sections, but includes some repetition of schema details. It is not overly long, but could be more concise by removing redundant param descriptions.

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

Completeness4/5

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

Given the presence of an output schema and clear parameter descriptions, the description covers the main retrieval scenarios and parameter options. It does not detail error handling beyond mentioning error return, but that is acceptable.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds value beyond schema by explaining the interplay between page_id, title, and space_key (e.g., if page_id provided, title/space_key ignored). Also clarifies the sample parameter behavior.

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

Purpose5/5

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

The description clearly states 'Get content of a specific Confluence page' and distinguishes the two lookup methods (by ID or by title+space_key). It sets the tool apart from siblings like search or get_comments.

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

Usage Guidelines4/5

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

Provides explicit guidance on when to use page_id versus title+space_key, including an example of where to find the page ID. However, it does not directly reference sibling tools or explicitly state when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SharkyND/mcp-atlassian'

If you have feedback or need assistance with the MCP directory API, please join our Discord server