Skip to main content
Glama
Sign In
mcp-jira-confluence-corp

mcp-jira-confluence-corp

by mshegolev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

confluence_get_page_by_title

Read-onlyIdempotent

Retrieve a Confluence page by its exact title and space key. Get page content including body storage and version details.

Instructions

Fetch a Confluence page by exact title within a space.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3/5.0
Behavior2/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds no behavioral context beyond aligning with 'Fetch'. Does not disclose error handling, authentication requirements, or rate limits.

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, well-structured sentence that front-loads the action and resource. No wasted words.

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?

Given the presence of a detailed input schema and an output schema (as indicated by context signals), the description provides sufficient high-level context. However, it could mention how the 'response_format' parameter affects output.

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?

The description does not mention any parameters. While the input schema provides detailed descriptions for each parameter, the tool description fails to add context like the need for exact title match or the space key requirement. With 0% schema description coverage from the description itself, it does not compensate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Fetch' and resource 'Confluence page by exact title within a space'. It distinguishes itself from sibling tools like 'confluence_get_page' (which likely uses page ID) and 'confluence_search', but does not explicitly mention these alternatives.

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 on when to use this tool vs alternatives like 'confluence_get_page' or 'confluence_search'. Does not specify prerequisites or context such as 'use when you know the exact title and space key'.

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