Skip to main content
Glama
Sign In
MCP Atlassian Server

MCP Atlassian Server

by dunz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_confluence_page_children

Retrieve hierarchical list of direct child pages under a specified Confluence parent page. Supports pagination and expanded properties.

Instructions

List child pages under a given Confluence page. Returns a hierarchical list of direct child pages.

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": {
      "pageId": "<pageId>"
    },
    "name": "list_confluence_page_children"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoThe maximum number of child pages to return. Default is 25, maximum is 100.
startNoThe starting index for pagination. Default is 0.
expandNoProperties to expand in the response.space
pageIdYesThe ID of the parent page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden of disclosing behavior. It states the return shape (a list of direct child pages) and implies a read-only operation, but it does not mention pagination behavior, what happens when a page has no children, permission requirements, or whether 'hierarchical' means nested objects beyond one level.

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 core action. The second sentence clarifies the output scope, though 'hierarchical list' and 'direct child pages' are slightly redundant or potentially ambiguous together.

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

Completeness3/5

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

For a simple listing tool with 4 parameters, the description is mostly adequate: it identifies the resource, the required pageId, and the response type. However, with no output schema and no annotations, it leaves some important context unspecified, such as pagination semantics and the exact meaning of 'hierarchical' in the response.

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 every parameter is already documented. The description adds no new parameter-level meaning beyond restating that the tool operates on a given parent page, matching pageId.

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 ('List'), a specific resource ('child pages under a given Confluence page'), and clarifies that it returns direct child pages. This clearly distinguishes it from sibling tools like list_confluence_page_ancestors or read_confluence_page.

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 makes the usage context clear: you call this when you have a parent Confluence page ID and want its child pages. It does not explicitly enumerate exclusions or alternative tools, but the 'direct child pages' wording provides enough context to avoid obvious misuse.

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

Deploy Server

Other Tools