Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_page

Add a new page to an existing ClickUp Doc, with optional nesting under a parent page and Markdown or plain text content.

Instructions

Add a page to an existing Doc (optionally nested under another page).

When to Use:

  • To append a new section/page to a Doc you already created or found.

When NOT to Use:

  • To create the Doc itself — use clickup_create_doc.

  • To modify an existing page — use clickup_edit_page.

Returns: A confirmation with the new page's name and id.

Examples:

  • params = {"doc_id": "8cbq...", "name": "Overview", "content": "# Hi"}

  • params = {"doc_id": "8cbq...", "name": "Detail", "parent_page_id": "abc"}

Error Handling: 404 → Doc/parent 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 indicate this is a write operation (readOnlyHint=false) but non-destructive (destructiveHint=false). The description adds that it returns a confirmation with name and id, and explains error handling for 404. This goes beyond annotations, though it could mention any required permissions or rate limits.

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-organized with clear sections: main action, when to use, when not to use, returns, examples, and error handling. 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 output schema exists (context signals), the description appropriately covers return behavior and error scenarios. Examples cover both top-level and nested page creation. All essential decision points are addressed.

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

Parameters4/5

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

The input schema provides detailed descriptions for all 7 parameters (name, doc_id, content, etc.), so the description doesn't need to repeat them. The description adds useful examples showing typical usage patterns, which helps the agent understand how to combine parameters.

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 verb 'Add a page to an existing Doc' and specifies optional nesting. It distinguishes from siblings like clickup_create_doc and clickup_edit_page in the 'When NOT to Use' section.

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?

Explicitly states when to use ('To append a new section/page to a Doc you already created or found') and when not to use, with references to alternative tools for creation and modification.

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