Skip to main content
Glama

Get Page Children

confluence_get_page_children
Read-only

Retrieve child pages and folders from a Confluence page by specifying its ID, with options to paginate, include content, and convert to markdown.

Instructions

Get child pages and folders of a specific Confluence page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of child items to return (1-50)
startNoStarting index for pagination (0-based)
expandNoFields to expand in the response (e.g., 'version', 'body.storage'). Defaults to 'version,history'.version,history
parent_idYesThe ID of the parent page whose children you want to retrieve
include_contentNoWhether to include the page content in the response
include_foldersNoWhether to include child folders in addition to child pages
convert_to_markdownNoWhether to convert page content to markdown (true) or keep it in raw HTML format (false). Only relevant if include_content is true.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation, and the description is consistent with that. It adds minor context by mentioning folders and page scoping, but does not disclose traits like direct-children-only behavior or pagination semantics beyond what the schema already covers.

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 a single sentence with no filler or redundancy. It is front-loaded with the action and resource, making the core operation immediately understandable.

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?

With readOnlyHint, a fully documented schema, and an output schema available, the definition is operationally self-sufficient. The main missing piece is guidance for choosing this tool over sibling tools, but that gap is already captured in the usage_guidelines dimension.

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?

All 7 parameters have descriptions in the schema, so schema coverage is 100%, which sets the baseline at 3. The description itself adds no parameter-level detail, so it provides no additional value beyond the structured schema.

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

Purpose4/5

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

States a specific verb (get), resource (child pages and folders), and scope (specific Confluence page). It is clear what the tool does, though it does not explicitly distinguish itself from sibling tools like get_space_page_tree.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. An agent must infer usage from the tool name and generic intent, which is especially weak given the large set of sibling tools.

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

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/Nikel-san/AtlMCPforDC'

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