Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_doc_pages

Read-onlyIdempotent

Retrieve all pages of a ClickUp Doc with their full content, including title, subtitle, and body in markdown or plain text. Use this to read an entire Doc in a single call.

Instructions

Fetch a Doc's pages with content (the full readable body of the Doc).

When to Use:

  • To read everything a Doc contains in one call.

When NOT to Use:

  • To read just one page — use clickup_get_page.

  • To see structure without content — use clickup_get_doc_page_listing.

Returns: Each page's title, subtitle, and content (markdown by default). Very large Docs are truncated with a note.

Examples:

  • params = {"doc_id": "8cbq...", "content_format": "text/plain"}

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 indicate readOnlyHint, idempotentHint, and destructiveHint, so the bar for additional disclosure is lower. The description adds valuable context: it returns title, subtitle, content (markdown default), mentions truncation for large Docs, and covers error handling (404). No contradiction with 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?

The description is concise and well-structured with distinct sections (purpose, usage guidelines, returns, example, error handling). Every sentence earns its place, and the critical information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that an output schema exists and the input schema is rich, the description covers key aspects: the core functionality, behavior for large Docs, error handling, and an example. It lacks detail on optional parameters like workspace_id and max_page_depth, but those are well-documented in the schema. Overall, it is sufficient for an agent to use correctly.

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?

The input schema already provides thorough descriptions for all parameters, so the description adds limited extra value. It includes an example with doc_id and content_format, which is helpful but not essential. The schema coverage being 100% effective (despite signal saying 0% in description text) sets a baseline of 3.

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 action (Fetch), the resource (Doc's pages with content), and explicitly distinguishes from siblings like clickup_get_page and clickup_get_doc_page_listing, making the tool's purpose unambiguous.

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?

The description provides explicit 'When to Use' and 'When NOT to Use' sections with specific alternative tools, giving the agent clear decision criteria for selecting this tool over others.

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