Skip to main content
Glama
Sign In
mcp-confluence

mcp-confluence

by sirexelite
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Обновить страницу

confluence_update_page

Update a Confluence page's title, body, or both. Version increments automatically on save.

Instructions

Обновляет заголовок и/или тело страницы. Номер версии инкрементируется автоматически.

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": {
      "id": "<id>"
    },
    "name": "confluence_update_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID страницы
bodyNoНовое тело в storage-формате (необязательно)
titleNoНовый заголовок (необязательно)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Beyond the schema, the description adds that the version number is incremented automatically, a helpful behavioral trait. However, it omits other details like error conditions (e.g., non-existent page) or permission requirements.

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?

The description is two short sentences, no wasted words, and front-loads the primary action. It is appropriately concise.

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

Completeness4/5

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

For a simple update tool with no output schema, the description is mostly complete: it covers what is updated and version behavior. However, it could mention that the page must exist and clarify the storage format for body.

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 parameter descriptions. The tool description reinforces that title and/or body can be updated but adds minimal new meaning beyond the schema.

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 explicitly states the tool updates the title and/or body of a page, clearly distinguishing it from sibling tools like create, delete, or get pages.

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 does not provide explicit when-to-use or when-not-to-use guidance. It implies usage for updating page title/body but offers no prerequisites or alternatives.

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

Deploy Server

Other Tools