Skip to main content
Glama

Get Page Children

confluence_get_page_children
Read-only

Retrieve child pages and folders from a Confluence page to navigate content structure, with options for pagination, content inclusion, and format conversion.

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 provide readOnlyHint=true, indicating a safe read operation. The description adds valuable context beyond this: it mentions pagination support via 'start' and 'limit', specifies that it returns both pages and folders (with an option to exclude folders), and notes content conversion to markdown. This enriches behavioral understanding without contradicting 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 front-loaded with the core purpose in the first sentence, followed by a structured breakdown of args and returns. While efficient, the parameter listing is somewhat redundant given the schema's completeness, slightly reducing conciseness. Overall, it's well-organized with minimal waste.

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 tool's moderate complexity (7 parameters), rich schema (100% coverage), annotations (readOnlyHint), and output schema (implied by 'Returns' statement), the description is complete enough. It covers the tool's scope, key parameters, and behavioral traits, providing adequate context for an agent to use it effectively.

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%, meaning all parameters are well-documented in the schema itself. The description lists parameters but doesn't add significant meaning beyond what the schema provides (e.g., it repeats 'parent_id' and 'limit' without extra insights). Baseline 3 is appropriate as the schema carries the full burden.

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 ('Get') and resource ('child pages and folders of a specific Confluence page'), making the purpose specific and actionable. It distinguishes itself from siblings like 'confluence_get_page' (which retrieves a single page) and 'confluence_get_space_page_tree' (which retrieves a tree structure for a space), establishing clear differentiation.

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 by specifying it retrieves children of a 'specific Confluence page', suggesting it's for hierarchical navigation. However, it lacks explicit guidance on when to use this tool versus alternatives like 'confluence_search' for broader queries or 'confluence_get_space_page_tree' for space-level hierarchies, leaving some ambiguity.

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