Skip to main content
Glama
Sign In
confluence-http-api-mcp

confluence-http-api-mcp

by rkorablin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

confluence_get_page

Retrieve a Confluence page by numeric content ID to get the title, space, ancestors, and plain-text body.

Instructions

Get a Confluence page by numeric content id. Returns title, space, ancestors and plain-text body.

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>"
    },
    "name": "confluence_get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYesContent id, e.g. 123456789
maxBodyCharsNoTruncate body text after N chars (default 12000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the safety burden. It explicitly states the return fields (title, space, ancestors, body) and that the body is plain-text, which is useful behavioral context. It does not mention authentication or error behavior, but for a get operation it is adequate.

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 a single sentence, front-loaded with the action and resource, and contains no redundant words. Every part earns its place.

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?

Although there is no output schema, the description covers the main return values. For a simple get-by-ID tool with two parameters, this is sufficient. It could briefly mention behavior like truncation via maxBodyChars, but the schema already handles that.

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% for both parameters, so the schema already documents them. The description adds only that the page is identified by a numeric ID, which is slightly redundant with the schema's example, so no significant extra meaning is provided.

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 uses the specific verb 'Get' with the resource 'Confluence page' and specifies the method 'by numeric content id'. This clearly distinguishes it from siblings like 'confluence_get_page_by_title'.

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

Usage Guidelines4/5

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

The description provides clear context that this tool is for retrieving pages when you have a numeric content ID, which implicitly suggests using it instead of title-based lookup. However, it does not explicitly name alternatives or state when not to use it.

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