Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_page

Read-onlyIdempotent

Fetch a single page from a ClickUp Doc by its page ID, returning its title, subtitle, and content in markdown format.

Instructions

Fetch one page of a Doc, including its content.

When to Use:

  • To read or re-read a single page by id (e.g. before editing it).

When NOT to Use:

  • To read every page — use clickup_get_doc_pages.

Returns: The page's title, subtitle, and content (markdown by default).

Examples:

  • params = {"doc_id": "8cbq...", "page_id": "abc"}

Error Handling: 404 → page 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, idempotentHint, and destructiveHint. The description adds value by detailing the return content (title, subtitle, markdown) and error handling (404), which enhances transparency beyond the 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 well-structured with clear sections (main action, usage, returns, examples, error handling). It is concise, front-loading the core purpose, and every sentence adds value.

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 presence of an output schema and 5 parameters, the description adequately covers return format, example usage, and error scenarios. It is complete for an agent to understand and invoke the tool 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 provides thorough descriptions for all parameters, so schema coverage is effectively high. The description does not add further meaning to the parameters beyond what is already in the schema, resulting in a baseline score 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 'Fetch one page of a Doc, including its content.' The verb 'Fetch' and resource 'page' are specific, and the distinction from sibling `clickup_get_doc_pages` is explicit.

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 includes explicit 'When to Use' and 'When NOT to Use' sections, directly telling the agent when to call this tool and when to use `clickup_get_doc_pages` instead, providing clear guidance.

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