Skip to main content
Glama
rafadepaula

@rafadepaula/clickup-mcp

by rafadepaula

clickup_get_document_pages

Retrieve the full content of specific ClickUp document pages by page ID, using discovered page IDs to fetch text or Markdown for review and processing.

Instructions

Get the full content of specific pages by page ID. Use list_document_pages first to discover available page IDs.

Input Schema

NameRequiredDescriptionDefault
page_idsYesArray of page IDs to retrieve (e.g. ['ad-2675877']). In ClickUp doc URLs, the page_id is the second ID after /docs/ or /v/dc/. If the URL contains only one ID (e.g. /{workspace_id}/docs/{document_id}), that is the document_id — use list_document_pages to discover page IDs.
document_idYesID of the document (e.g. 'ad-909705'). In ClickUp doc URLs the path is either /{workspace_id}/docs/{document_id}/{page_id} or /{workspace_id}/v/dc/{document_id}/{page_id}. The document_id is always the first ID after /docs/ or /v/dc/.
workspace_idNoWorkspace ID (digits only). Only needed when you have multiple workspaces.
content_formatNoResponse content format.text/plain

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses that this is a content-retrieval operation and that page IDs must be discovered first, but it does not mention permissions, rate limits, response size, or error behavior.

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?

Two sentences, front-loaded, with zero wasted text. The discovery prerequisite follows immediately after the purpose.

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?

For a straightforward read tool with a fully described input schema and no output schema, the description provides enough context to invoke it correctly. It could additionally mention return format or expected content shape, but the schema's content_format parameter covers format selection.

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 parameter semantics are already well documented, including the ClickUp URL mapping for document_id and page_ids. The description adds only the page-ID prerequisite and no additional parameter detail.

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?

States a specific verb and resource ('Get the full content of specific pages by page ID') and distinguishes itself from the discovery sibling by directing the agent to list_document_pages first.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives clear prerequisite guidance: use list_document_pages first to discover page IDs. It does not name when-not-to-use cases or other alternatives, but the routing context is explicit.

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