Skip to main content
Glama

confluence_get_page_children

Retrieve child pages of a specific Confluence parent page. Supports pagination, content inclusion, and markdown conversion.

Instructions

Get child pages of a specific Confluence page.

Args: ctx: The FastMCP context. parent_id: The ID of the parent page. expand: Fields to expand. limit: Maximum number of child pages. include_content: Whether to include page content. convert_to_markdown: Convert content to markdown if include_content is true. start: Starting index for pagination.

Returns: JSON string representing a list of child page objects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of child pages to return (1-50)
startNoStarting index for pagination (0-based)
expandNoFields to expand in the response (e.g., 'version', 'body.storage')version
parent_idYesThe ID of the parent page whose children you want to retrieve
include_contentNoWhether to include the page content in the response
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
Behavior4/5

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

No annotations exist, so the description carries the burden. It explains pagination (start, limit), optional content inclusion, and markdown conversion, giving a clear behavioral picture. However, it does not mention ordering, recursion depth, or performance characteristics, which are minor omissions.

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 well-structured with Args and Returns sections, and each parameter is listed clearly. It is slightly verbose due to parameter duplication with the schema, but overall concise and easy to parse.

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 presence of an output schema (not shown but indicated), the description adequately covers the tool's behavior. All parameters are documented, pagination is addressed, and optional behaviors are specified. No obvious gaps for a retrieval tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining that convert_to_markdown is only relevant if include_content is true, and it lists parameters in order with brief clarifications beyond the schema descriptions.

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 'Get child pages of a specific Confluence page,' which is a specific verb-resource pair. It distinguishes itself from sibling tools like confluence_get_page (single page) and confluence_search (search across pages).

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 for fetching children given a parent_id, but does not explicitly state when to use this over alternatives or mention any prerequisites or exclusions. Sibling tools are many, but no guidance is provided.

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/SharkyND/mcp-atlassian'

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