Skip to main content
Glama

manage_pages

Perform various Confluence page operations: get, list, create, update, delete, move, and diff pages with support for versioning and content formatting.

Instructions

Unified tool for Confluence page operations (get, get_by_title, list, get_children, get_ancestors, list_versions, diff)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: 'get', 'get_by_title', 'list', 'create', 'update', 'delete', 'get_children', 'get_ancestors', 'list_versions', 'move', 'diff'
page_idNoPage ID (required for get, update, delete, get_children, get_ancestors, move, diff)
space_idNoSpace ID (required for list, create, get_by_title)
titleNoPage title (required for create, get_by_title; optional for update)
bodyNoPage body content (for create, update). Accepts markdown by default (# headings, **bold**, *italic*, [links](url), - lists, | tables). Set content_format='storage' to pass raw Confluence XHTML instead.
content_formatNoFormat of body content: 'markdown' (default) or 'storage' for raw Confluence XHTML. When using markdown: # for headings, **bold**, *italic*, \x60code\x60, [text](url) for links, - for lists, | for tables.
parent_idNoParent page ID (for create)
versionNoPage version number (required for update, move — must be current version + 1)
statusNoPage status: 'current', 'draft' (for create, update, list filter)
body_formatNoBody format to return: 'storage', 'atlas_doc_format', 'view'
limitNoNumber of results per page (default 25)
cursorNoPagination cursor for next page
sortNoSort order for list (e.g., '-modified-date', 'title')
target_space_idNoTarget space ID (for move)
target_parent_idNoTarget parent page ID (for move)
from_versionNoStarting version number (required for diff)
to_versionNoEnding version number (required for diff)
Behavior2/5

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

No annotations are present, so the description must disclose behavioral traits. It simply lists operations without describing side effects, idempotency, authentication needs, or what happens during creation/updates/deletion.

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 a single sentence, which is concise but omits important information (e.g., all actions). It is not well-structured for a tool with many parameters and actions.

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

Completeness2/5

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

Given the complexity (17 parameters, 11 actions, no output schema), the description is insufficient. It does not explain the unified nature, how actions are chosen, or what return values look like.

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 description coverage is 100%, but the description adds extra value for 'body' and 'content_format' by explaining markdown syntax and storage format. This goes beyond the schema descriptions.

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

Purpose3/5

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

The description states it's a 'unified tool for Confluence page operations' and lists several actions, but omits key actions like 'create', 'update', 'delete', 'move' from the description, which are present in the schema. This partial listing reduces clarity.

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?

No guidance is provided on when to use this tool vs. sibling tools (e.g., manage_attachments, manage_comments). There is no mention of context, prerequisites, or alternatives.

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/zach-snell/ctk'

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