Skip to main content
Glama
Sign In
JIRA MCP Server

JIRA MCP Server

by CarloDeStefano90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

confluence_update_page

Update the content and optionally the title of an existing Confluence page using storage XHTML format.

Instructions

Aggiorna il contenuto di una pagina Confluence esistente.

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

Input Schema

NameRequiredDescriptionDefault
titleNoNuovo titolo (opzionale, mantiene il precedente se omesso)
pageIdYesID della pagina da aggiornare
contentYesNuovo contenuto in formato storage XHTML

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It only states 'updates content' without disclosing potential side effects, error conditions, permissions required, or whether content is replaced or appended.

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 a single sentence with no extraneous information. It is concise, but could be more informative without becoming verbose.

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 absence of an output schema and annotations, the description does not sufficiently explain the full context of the operation, such as return values, error handling, or behavior when the page ID is invalid.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, but the tool description does not add any meaning beyond what the schema already provides. It simply repeats the update action without elaborating on parameter usage or constraints.

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 'Aggiorna il contenuto di una pagina Confluence esistente' (Updates the content of an existing Confluence page), specifying the verb and resource. It distinguishes the tool from siblings like create_page and get_page.

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 versus alternatives, prerequisites (e.g., page must exist), or conditions for use. The description lacks context for appropriate invocation.

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