Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_doc

Create a ClickUp Doc and place it directly inside a Space, Folder, List, or Workspace by specifying a parent type and ID. Avoids the need to create then move.

Instructions

Create a Doc, optionally placed directly in its final location.

Set parent_id + parent_type to create the Doc inside a Space, Folder, List, the Everything level, or the Workspace root in one call — no create-then-drag. The parent type maps to ClickUp's numeric enum: space→4, folder→5, list→6, everything→7, workspace→12. Omit both parent fields to create the Doc in the default (private) location.

When to Use:

  • To start a new Doc where it belongs (e.g. a spec Doc inside a project List).

When NOT to Use:

  • To add a page to an existing Doc — use clickup_create_page.

  • To change an existing page's text — use clickup_edit_page.

Returns: A confirmation with the new Doc's name, id, and parent location.

Examples:

  • params = {"name": "Q3 Spec", "parent_id": "901300", "parent_type": "list"}

  • params = {"name": "Scratch", "create_page": false}

Error Handling: 400 → bad parent id/type pairing; 404 → parent not found. Errors return an Error ... string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description explains the placement behavior (optional parent_id/parent_type) and default location. It also describes error responses. Annotations do not contradict; the tool's behaviors are fully disclosed.

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, well-structured with clear sections, and front-loads the primary action. Every sentence adds value without redundancy.

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 parameter count and complexity, the description is complete: it covers usage, placement logic, alternatives, returns, error handling, and examples. Output schema is said to exist, so return values are covered.

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

Parameters5/5

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

Schema descriptions already provide meaning for each parameter. The description adds valuable context like the numeric enum mapping for parent_type and the default behavior for missing parent fields, enhancing understanding beyond schema.

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 tool creates a Doc, optionally placing it in a specific location. It distinguishes from siblings like clickup_create_page and clickup_edit_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?

The description includes explicit 'When to Use' and 'When NOT to Use' sections, naming specific alternative tools. Examples and error handling further guide correct usage.

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