Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_doc_page_listing

Read-onlyIdempotent

List a ClickUp Doc's page hierarchy to retrieve page IDs and titles without fetching content. Quickly navigate document structure.

Instructions

List a Doc's page tree (titles and ids only, nested — no content).

A lightweight outline of the Doc: the hierarchy of pages and subpages with their ids, without fetching any body text.

When to Use:

  • To see a Doc's structure and grab a specific page id cheaply.

When NOT to Use:

  • To read page content — use clickup_get_doc_pages or clickup_get_page.

Returns: An indented tree of page names and ids.

Examples:

  • params = {"doc_id": "8cbq...", "max_page_depth": 2}

Error Handling: 404 → Doc not found. Errors return an Error ... string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds context: lightweight outline, returns tree of names/ids, error handling (404). Does not contradict annotations.

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?

Well-structured with clear sections (purpose, when to use, returns, examples, errors). Front-loaded with essential info, no wasted words.

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 simplicity, output schema exists, and annotations cover safety, the description adequately explains return values (tree of names/ids) and error behavior. No gaps.

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

Parameters2/5

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

Schema description coverage is 0%, so description must compensate for parameter details. It only provides a single example showing doc_id and max_page_depth, but does not explain workspace_id, response_format, or parameter semantics beyond what the schema already provides. The schema itself has good descriptions, but the description fails to add value.

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 'List a Doc's page tree (titles and ids only, nested — no content)', specifying the verb (list), resource (Doc page tree), and scope. It distinguishes from siblings like clickup_get_doc_pages (which fetches content) and clickup_get_page (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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit 'When to Use' (see structure, grab page IDs cheaply) and 'When NOT to Use' (read content, with alternatives named). This directly guides tool selection.

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/trustxai/clickup-mcp'

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