mcp-confluence

Найти страницу по заголовку

confluence_get_page_by_title

Retrieve a Confluence page by specifying the space key and exact page title.

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

Input Schema

Name	Required	Description	Default
`title`	Yes	Точный заголовок страницы
`spaceKey`	Yes	Ключ пространства, например DEV

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 10, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the tool 'finds' a page, without mentioning what happens if the page is not found (e.g., returns null, error), authentication requirements, rate limits, or any side effects. This is minimal for a read tool.

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, highly concise. It front-loads the core purpose without extraneous content. However, it could benefit from a brief note on exactness or behavior on no match without becoming verbose.

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?

Given the simplicity of the tool (2 parameters, no output schema, no nested objects), the description adequately states the purpose. However, it lacks details about the return value or handling of missing pages, leaving some completeness gaps for a fully self-contained definition.

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% and parameter descriptions already specify 'exact page title' and 'space key'. The description adds the word 'exact' which reinforces the schema's precision, but does not add new semantic meaning beyond what is already in the schema. Baseline 3 is appropriate.

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 finds a page by space key and exact title. The verb 'ищет' (searches) and resources 'ключу пространства и точному заголовку' (space key and exact title) specify the exact action and parameters, distinguishing it from siblings like confluence_search or confluence_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?

The description provides no guidance on when to use this tool versus alternatives like confluence_search (for non-exact matches) or confluence_get_page (by ID). It neither states prerequisites nor excludes scenarios, leaving the agent to infer usage from the tool name alone.

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

Deploy Server