Skip to main content
Glama

Get Page

confluence_get_page
Read-only

Retrieve content of a Confluence page by ID, URL, 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, full page URL, or tiny link. 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).

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.
page_idNoConfluence page ID, full page URL, or tiny link. For example: '123456789', 'https://example.atlassian.net/wiki/spaces/TEAM/pages/123456789/Page+Title', or 'https://example.atlassian.net/wiki/x/N4CIO'. 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
Behavior5/5

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

Consistent with annotations (readOnlyHint=true), adds context about return format (JSON string), metadata options, markdown vs HTML conversion, and token usage warning for HTML.

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

Conciseness5/5

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

Well-structured with clear Args section, no fluff, each sentence adds value.

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

Completeness5/5

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

Covers all needed aspects: identification methods, output format, metadata and conversion options, with an output schema present to handle return details.

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

Parameters5/5

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

Adds significant meaning beyond the input schema: explains that page_id can be ID, URL, or tiny link, and describes mutual exclusivity. Schema coverage is 100% and description enriches each parameter.

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 the tool gets content of a specific Confluence page by ID or title+space, which distinguishes it from sibling tools like create, update, search, etc.

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 clear guidance on when to use page_id vs title/space_key, but does not explicitly differentiate from other retrieval tools like confluence_search or get_page_children.

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/GeiserX/atlassian-browser-mcp'

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