Skip to main content
Glama

confluence_search

Search and retrieve Confluence content using CQL queries via the MCP Atlassian Server, enabling efficient access to Confluence data within the MCP interface.

Instructions

Search Confluence content using CQL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoResults limit (1-50)
queryYesCQL query string

Implementation Reference

  • Handler for the 'confluence_search' tool call. Parses arguments, executes Confluence search API request using CQL query, maps and formats results into JSON text content for response.
    case 'confluence_search': {
      const { query, limit = 10 } = request.params.arguments as any;
      const response = await this.confluenceAxios.get('/content/search', {
        params: {
          cql: query,
          limit: limit,
          expand: 'space'
        }
      });
    
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(response.data.results.map((r: any) => ({
            id: r.id,
            title: r.title,
            type: r.type,
            space: r.space?.name,
            url: `${CONFLUENCE_URL}${r._links?.webui}`,
            lastModified: r.history?.lastUpdated?.when
          })), null, 2)
        }]
      };
    }
  • src/index.ts:72-93 (registration)
    Registration of the 'confluence_search' tool in the ListTools handler, including name, description, and input schema definition.
        {
          name: 'confluence_search',
          description: 'Search Confluence content using CQL',
          inputSchema: {
            type: 'object',
            properties: {
              query: {
                type: 'string',
                description: 'CQL query string'
              },
              limit: {
                type: 'number',
                description: 'Results limit (1-50)',
                minimum: 1,
                maximum: 50
              }
            },
            required: ['query']
          }
        }
      ]
    }));
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'CQL' (Confluence Query Language) but doesn't disclose behavioral traits like pagination, rate limits, error handling, or what happens with invalid queries. The description is minimal and lacks critical operational context for a search 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, efficient sentence with zero waste, making it appropriately sized and front-loaded. However, it's overly concise to the point of under-specification, lacking necessary details for effective use, which slightly reduces its score from perfect.

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 no annotations, no output schema, and a search tool with potential complexity (CQL queries), the description is incomplete. It doesn't explain return values, error cases, or behavioral nuances, leaving significant gaps for an AI agent to understand how to invoke and interpret results effectively.

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 description coverage is 100%, with clear documentation for 'query' (CQL query string) and 'limit' (results limit 1-50). The description adds no additional parameter semantics beyond what the schema provides, such as CQL syntax examples or default behaviors. Baseline 3 is appropriate as the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Search Confluence content using CQL' clearly states the action (search) and resource (Confluence content), but it's vague about what 'content' specifically includes (pages, blogs, spaces, etc.) and doesn't distinguish from sibling tool 'jira_search'. It provides a basic purpose but lacks specificity about scope.

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. The description doesn't mention the sibling 'jira_search' tool or any other search methods, nor does it specify prerequisites like authentication or appropriate contexts for CQL queries. Usage is implied through the name but not explicitly stated.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/petrsovadina/mcp-atlassian'

If you have feedback or need assistance with the MCP directory API, please join our Discord server