Skip to main content
Glama
karbassi

confluence-adf-mcp

by karbassi
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

confluence_archive_page

Archive a Confluence page to remove it from active view. Preview mode shows changes; confirm to execute permanently.

Instructions

Archive a Confluence page.

DESTRUCTIVE: This removes the page from active view. By default this tool
runs in preview mode — call with confirm=True to actually archive.

You MUST show the preview to the user and get their explicit approval before
calling again with confirm=True.

Args:
    page_id: A numeric page ID or a Confluence URL (including short /wiki/x/ links).
    confirm: Must be True to actually archive. False (default) shows a preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNo
page_idYes

Tool Definition Quality

A5/5.0
Behavior5/5

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

Despite no annotations, the description transparently discloses destructive behavior ('removes page from active view'), preview mode, and the need for user consent. Fully covers behavioral traits.

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?

Concise, front-loaded with purpose, then warnings, then parameter details. No wasted sentences; every line 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?

Given no output schema or annotations, the description sufficiently covers purpose, usage, behavior, and parameters. Complete for a straightforward tool.

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?

With 0% schema description coverage, the description fully explains both parameters: page_id accepts numeric ID or Confluence URL (including short links), confirm controls preview vs actual action.

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's action: 'Archive a Confluence page.' It distinguishes from sibling tools like create, delete, and edit by focusing on archiving behavior.

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

Usage Guidelines5/5

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

Explicitly instructs to show preview to user and obtain approval before confirming. Clearly separates preview mode (confirm=False) from actual archive (confirm=True), guiding agent workflow.

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/karbassi/confluence-adf-mcp'

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