Skip to main content
Glama
Sign In

Confluence

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Confluence List Pages

confluence_list_pages
Read-onlyIdempotent

List all pages in a Confluence space. Returns page ID, title, status, and version. Specify space key (e.g., "ENG", "SALES").

Input Schema

NameRequiredDescriptionDefault
sortNoSort order: "created-date", "-created-date", "modified-date", "-modified-date", "title" (default: "-modified-date")
limitNoNumber of pages to return (default 25, max 100)
space_idYesSpace ID to list pages from

Output Schema

NameRequiredDescriptionDefault
pagesYesList of pages in the space

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "pages": {
+      "description": "List of pages in the space",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "pages"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 25,
+    "space_id": "ENG"
+  },
+  {
+    "limit": 50,
+    "sort": "title",
+    "space_id": "SALES"
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds minor value by listing the returned fields, but does not provide significant behavioral context beyond the annotations.

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 extremely concise at two sentences, with the purpose front-loaded. Every word adds value and there is no wasted text.

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

Completeness5/5

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

Given the existence of an output schema, the description appropriately focuses on the essential input (space_id) and return fields. It is complete for a list tool with well-documented parameters and annotations.

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?

The input schema has 100% coverage on all three parameters. The description does not add extra meaning beyond what the schema already provides, so it meets the baseline expectation.

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 clearly states the verb 'List', the resource 'pages in a Confluence space', and specifies the returned fields (page ID, title, status, version). It effectively distinguishes from siblings like confluence_get_page (single page) and confluence_search (search).

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

Usage Guidelines4/5

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

The description provides clear context on when to use the tool: to list all pages in a space by specifying the space key. However, it does not explicitly mention when not to use it or suggest alternatives like confluence_search for more targeted queries.

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

All Confluence toolsInspect
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