Skip to main content
Glama
Sign In
Confluence MCP Server

Confluence MCP Server

by aaronsb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

find_confluence_page

Find a Confluence page by exact title and retrieve its content in markdown format with metadata. Optionally specify a space ID to narrow search. Returns a list if multiple pages match.

Instructions

Find and retrieve a Confluence page by its title. Returns the page content in markdown format, along with metadata. Optionally specify a spaceId to narrow the search. If multiple pages match the title, returns a list of matches to choose from. TIP: Use this when you know the exact page title, but prefer search_confluence_pages for partial matches.

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

Input Schema

NameRequiredDescriptionDefault
titleYesTitle of the page to find
spaceIdNoOptional space ID to limit the search scope

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, but description discloses return format (markdown content, metadata) and behavior for multiple matches (returns list). Could be more explicit about read-only nature, but adequately transparent for a retrieval tool.

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?

Two sentences plus a tip, front-loaded with key action. No unnecessary words. Highly efficient.

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?

No output schema, but description explains return format. With sibling tools listed, provides sufficient context for agent to decide. Missing details on response structure (e.g., specific metadata fields), but acceptable for a simple retrieval tool.

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% with clear descriptions for both parameters. Description adds minimal value beyond schema, just reiterates title and optional spaceId. 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?

Clearly states 'Find and retrieve a Confluence page by its title' with specific verb and resource. Distinguishes from sibling 'search_confluence_pages' by mentioning exact title vs partial matches.

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

Usage Guidelines5/5

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

Explicitly advises when to use ('when you know the exact page title') and when to use alternative ('prefer search_confluence_pages for partial matches'). Also notes optional spaceId to narrow scope.

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