MCP Atlassian Server

confluence_search

Retrieve Confluence content such as pages, blogs, and attachments by executing CQL queries, with optional space filtering and result limits.

Instructions

Search for content in Confluence using CQL (Confluence Query Language)

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": {
      "query": "<query>"
    },
    "name": "confluence_search"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of results to return (default: 10)
`query`	Yes	CQL query to search for content
`spaceKey`	No	Optional space key to limit search to a specific space

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 18, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden, but it only states what the tool does. It does not disclose behavioral traits such as rate limits, pagination behavior, authentication requirements, or whether results are filtered by user permissions. The agent gets no behavioral context beyond the verb 'search'.

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 short and front-loaded with the key purpose. However, it could benefit from a brief expansion to add usage or behavioral guidance without losing conciseness.

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

Completeness2/5

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

Given the tool has no output schema and no annotations, the description is incomplete. The agent lacks information about return format, error handling, CQL syntax considerations (especially for complex queries), and pagination. For a search tool with a powerful but unfamiliar query language, more context is essential.

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%, so baseline is 3. The description adds no parameter-specific meaning beyond the schema; 'CQL' is mentioned but not explained, and 'spaceKey' meaning is clear from the schema. The description does not compensate beyond what is already documented.

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 identifies the tool as a search function for Confluence using CQL, which is more specific than a generic 'search'. It distinguishes from sibling tools like confluence_get_page (retrieving by ID) and Jira tools.

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 is provided on when to use this tool versus alternatives like jira_search_issues or when CQL is appropriate. The usage context is implied but lacks explicit when-to-use or when-not-to-use statements.

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

Deploy Server