confluence-http-api-mcp

confluence_get_page_by_title

Find a Confluence page by space key and exact title, returning the first match's content. Useful for fetching specific pages without browsing the page tree.

Instructions

Get a page by space key and exact title (first match).

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": {
      "spaceKey": "<spaceKey>",
      "title": "<title>"
    },
    "name": "confluence_get_page_by_title"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Exact page title
`spaceKey`	Yes	Space key, e.g. GAR
`maxBodyChars`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 6, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does reveal 'exact title' and 'first match' behavior, which is a useful nuance. However, it omits behavioral traits like response content truncation via maxBodyChars or error behavior when no match is found.

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, succinct sentence that conveys the core purpose without any filler or unnecessary detail. Every word contributes to understanding the tool.

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

Completeness3/5

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

The description is adequate for a simple getter but leaves gaps: it does not explain the effect of maxBodyChars on the returned content, nor does it clarify when to use this tool over the sibling 'confluence_get_page'. The absence of an output schema increases the need for such context.

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?

The description restates spaceKey and exact title, which largely duplicates the schema's existing parameter descriptions. It adds no additional meaning for the maxBodyChars parameter, and with 67% schema coverage, the description could have compensated but does not.

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 verb ('Get'), resource ('a page'), and key parameters ('space key' and 'exact title'). The 'first match' qualifier adds distinguishing scope, making it clear this is a direct lookup by title rather than a search.

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 implies usage when you have a space key and exact title, but it does not explicitly state when to use this tool over siblings like 'confluence_search' or 'confluence_get_page'. No alternatives or exclusions are mentioned.

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

Deploy Server