Skip to main content
Glama
aaronsb

Confluence Cloud MCP Server

manage_confluence_page

Create, read, update, delete, move, copy, archive, and edit Confluence pages. Manage labels and content properties.

Instructions

Get, create, update, delete, move, copy, archive, or pull pages for editing. Manage labels and content properties. Create returns a scratchpad for composing content before publishing. Use pull_for_editing to load existing page content into a scratchpad. Archive/unarchive pages or entire page trees.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesThe operation to perform
pageIdNoPage ID (required for get, update, delete, move, copy, get_versions, pull_for_editing, archive, archive_tree, unarchive)
spaceIdNoSpace ID (required for create, usable for list_archived)
spaceKeyNoSpace key (for list_archived)
titleNoPage title (required for create, optional for update)
parentIdNoParent page ID (optional for create, required for move, optional for copy)
expandNoAdditional data to include in the response
labelsNoLabels to add (for add_labels operation)
labelNoLabel to remove (for remove_label operation)
propertyKeyNoContent property key (for get_property, set_property, delete_property)
propertyValueNoContent property value as JSON object (for set_property)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions behavior like scratchpad creation and archive operations, but lacks disclosure of auth needs, rate limits, destructive nature of delete/archive operations, or response format. This is insufficient for safe invocation.

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 efficient, listing operations in a single line then adding key details about scratchpad and archiving. It is front-loaded with the most important information and avoids redundancy.

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?

Despite the tool's complexity (11 parameters, 19 operations), the description lacks guidance on when to use each operation, error handling, output structure, and prerequisites. Without an output schema, the agent lacks essential context for proper invocation.

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 coverage is 100% with clear descriptions for all parameters. The description adds context about scratchpad creation and label/property management, but does not significantly enhance parameter understanding beyond the schema. Baseline of 3 is appropriate.

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 manages Confluence pages with a comprehensive list of operations (get, create, update, delete, move, copy, archive, etc.), distinguishing it from sibling tools that handle content editing, media, or spaces.

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

Usage Guidelines3/5

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

The description provides internal guidance (e.g., 'Use pull_for_editing to load existing page content into a scratchpad'), but does not explicitly compare this tool to siblings like 'edit_confluence_content' or 'manage_confluence_space', leaving the agent to infer when to use 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/aaronsb/confluence-cloud'

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