Opsphere — DevOps & SRE Intelligence

Search Confluence pages

confluence_search

Read-only

Searches pages in Confluence using CQL (text + title match). Returns page IDs, titles, URLs and excerpts. Use confluence_page_read to get the full content of a result.

Input Schema

Name	Required	Description
`limit`	No	Max results to return (default 10, max 25)
`query`	Yes	Text to search for (e.g. "dump and restore", "deploy process")
`spaceKey`	No	Confluence space key (optional if set on default cloud account as confluence_space, or via CONFLUENCE_SPACE / CONFLUENCE_SPACE_KEY)
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	Yes
`contractVersion`	Yes
`dataSchemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 26, 2026

changedOutput schema / properties / data / additionalProperties
```
Previous value: -trueNew value: +false
```

changedOutput schema / properties / data / properties / items / items / additionalProperties

Previous value: -trueNew value: +{
+  "type": [
+    "string",
+    "number",
+    "boolean",
+    "null"
+  ]
+}

removedOutput schema / properties / data / properties / items / items / properties
```
Removed value: -{}
```
addedOutput schema / properties / data / properties / payloadJson
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / dataSchemaVersion

Added value: +{
+  "const": 1,
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "contractVersion",
-  "ok",
-  "data"
-]New value: +[
+  "contractVersion",
+  "dataSchemaVersion",
+  "ok",
+  "data"
+]

First observedOct 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (read-only, non-destructive, not open-world), so the description does not need to repeat that. It adds useful behavioral context by stating that results contain page IDs, titles, URLs and excerpts rather than full content, and it signals that full content requires a separate call.

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 three short sentences with no wasted content. It is front-loaded with the core search behavior and follows immediately with return behavior and the correct follow-up tool.

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?

The tool has an output schema and full schema coverage, so the description need not document every return field or parameter detail. It covers the essential search behavior and the handoff to confluence_page_read; only minor details such as pagination or result ordering are left implicit.

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%, so the parameters are already documented in the schema. The description only adds that queries use CQL text and title matching; it does not explain limit, spaceKey, or context_id beyond what the schema provides, which is the baseline expectation when schema coverage is complete.

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 states a specific verb and resource: searches Confluence pages using CQL with text and title matching. It also distinguishes the result from full page content by naming confluence_page_read as the follow-up tool for full content.

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?

It explicitly routes agents to confluence_page_read when they need the full content of a search result, which is the key usage decision for this tool. Combined with the clear search purpose, this gives agents enough guidance to choose correctly between search and page retrieval.

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

All Opsphere — DevOps & SRE Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?