Skip to main content
Glama

Get Page Children

confluence_get_page_children
Read-only

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

Instructions

Get child pages and folders 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 items. include_content: Whether to include page content. convert_to_markdown: Convert content to markdown if include_content is true. start: Starting index for pagination. include_folders: Whether to include child folders (default: True).

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

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate readOnlyHint=true, so the description need not repeat that. The description adds behavioral details such as support for pagination (start, limit parameters) and content conversion (markdown vs HTML), which are not in annotations.

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 a clear summary followed by a parameter list. It is concise but could be slightly more streamlined by leveraging the schema descriptions instead of duplicating them.

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 and annotations, the description adequately covers all necessary contextual information: it explains the return format (JSON string), pagination, and content conversion options. No gaps remain.

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?

The input schema provides 100% coverage with descriptions for all 7 parameters. The description adds value by clarifying the relationship between 'include_content' and 'convert_to_markdown' (e.g., 'Convert content to markdown if include_content is true'), which is not fully captured in the schema.

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 tool retrieves child pages and folders of a specific Confluence page, using a specific verb and resource. This distinguishes it from sibling tools like 'confluence_get_page' which retrieves a single page.

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 retrieving page hierarchy but does not explicitly state when to use this tool versus alternatives like 'confluence_search' or 'confluence_get_space_page_tree'. No exclusions or prerequisites are 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/GeiserX/atlassian-browser-mcp'

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