Opsphere — DevOps & SRE Intelligence

Read a Confluence page

confluence_page_read

Read-only

Reads the full content of a Confluence page and converts it to Markdown. Supports pagination via contentOffset/maxChars for large pages. Supply either pageId (from confluence_search) or title.

Input Schema

Name	Required	Description
`title`	No	Exact page title. Provide this OR pageId.
`pageId`	No	Page ID (from confluence_search results). Provide this OR title.
`maxChars`	No	Max characters to return per call (default 8000). Use with contentOffset for pagination.
`spaceKey`	No	Confluence space key when using title lookup (optional if set on default cloud account or env 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.
`contentOffset`	No	Character offset to start reading from (default 0). Use nextOffset from previous response to paginate.

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/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, non-destructive, closed-world operation. The description adds useful behavioral detail beyond annotations: content is converted to Markdown and large pages are paginated via contentOffset/maxChars. It does not discuss permissions or error behavior, but that gap is less critical given the annotation coverage.

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, front-loaded with the core action and output format, followed by pagination and lookup guidance. Every sentence adds useful information without waste.

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, rich annotations, and full schema-description coverage, so the description need not explain return values or every parameter. It covers the essential purpose, output format, and pagination behavior; however, it omits any mention of spaceKey fallback or context_id, relying entirely on the schema for those edge cases.

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 schema already documents all six parameters thoroughly. The description reinforces the pageId/title mutual exclusivity and pagination mechanics, but adds little beyond what the schema provides. 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?

The description states a specific verb and resource: 'Reads the full content of a Confluence page' and adds the output format ('converts it to Markdown'). It also distinguishes this tool from confluence_search by noting that pageId comes from search results, so an agent can tell the read tool apart from the search sibling.

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

Usage Guidelines3/5

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

The description implies usage by saying 'Supply either pageId (from confluence_search) or title,' which hints that search precedes reading. However, it does not explicitly state when to use this tool versus confluence_search, nor does it give clear inclusion/exclusion criteria.

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?