Skip to main content
Glama

Get Page Children

confluence_get_page_children
Read-onlyIdempotent

Retrieve child pages and folders for a specified Confluence parent page to list or navigate page hierarchies, with pagination, content expansion, and optional Markdown conversion.

Instructions

Get child pages and folders of a specific Confluence page.

Input 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')version
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

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.1
    • addedInput schema / additionalProperties
      Added value: +false
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  2. Addedv1.0.1

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false. The description adds no behavioral context beyond the basic purpose, such as pagination behavior, permission requirements, or default inclusion of folders.

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 front-loaded sentence with no wasted words. It is appropriately concise for a simple retrieval tool.

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?

The core purpose is present, and the rich schema plus output schema cover invocation details. However, the description omits how this tool relates to sibling page-tree tools and does not mention pagination or default folder inclusion, leaving some selection context to inference.

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 all seven parameters are already documented in the input schema. The description does not add meaning beyond the schema, which is acceptable given the high coverage baseline.

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?

The description states a specific verb and resource: getting child pages and folders of a specific Confluence page. It is clear what the tool returns, but it does not distinguish this from sibling tools like confluence_get_space_page_tree or confluence_get_page.

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?

There is no guidance on when to use this tool versus alternatives such as confluence_get_space_page_tree or confluence_get_page. No prerequisites, exclusions, or contextual triggers are provided; usage is only implied by the name.

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