Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

atlassian-mcp__confluence_edit_page

Destructive

Update an existing Confluence page. Content must be in XHTML storage format. If version is not provided the current version is fetched and auto-incremented.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "page_id": "<page_id>",
      "title": "<title>",
      "content": "<content>"
    },
    "name": "atlassian-mcp__confluence_edit_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesNew title for the page.
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
contentYesNew body in XHTML storage format.
page_idYesThe ID of the page to update.
versionNoVersion number for the update. If omitted the current version is auto-incremented.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: content must be XHTML storage format, and omitting version triggers a fetch plus auto-increment. It stops short of saying the page body is wholesale replaced, which is the concrete destructive consequence.

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?

Three short sentences, zero filler, and the core action is front-loaded before the format constraint and version behavior. Every sentence carries actionable information.

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?

For a 5-parameter mutation with a fully documented schema, no output schema, and annotations carrying the destructive flag, the description supplies the two non-obvious facts an agent needs (content format and version handling). Nothing required to call it correctly is missing.

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%, so all five parameters, including page_id, title, content, version, and account, are already documented. The description restates the version auto-increment behavior already present in the schema and adds only the XHTML format constraint, so it is a baseline-3 case.

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

Purpose4/5

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

States a specific verb and resource: 'Update an existing Confluence page.' The word 'existing' implicitly separates it from confluence_create_page and the destructive siblings, but no sibling is named explicitly, so differentiation relies on inference.

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?

Usage is implied by 'existing page' (use create_page for new pages, get_page for reads) but never stated. There is no explicit when-to-use/when-not guidance, prerequisites, or pointer to alternatives among the many confluence_* siblings.

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

All DataToRAG toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources