Skip to main content
Glama
Sign In
ClickUp MCP Server

ClickUp MCP Server

by azukhrufy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_doc

Create a new document in a ClickUp workspace by providing a name and content, optionally placing it under a space, folder, or list.

Instructions

Create a new ClickUp Doc in a team/workspace.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "team_id": "<team_id>",
      "name": "<name>"
    },
    "name": "create_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the doc
parentNoWhere to place the doc
contentNoContent of the doc
team_idYesThe ID of the team (workspace)
content_typeNoContent type (default text)
create_default_contentNoCreate default content blocks

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states the action ('Create a new ClickUp Doc') without mentioning mutational side effects, required permissions, default content behavior, or what the response contains. This is thin for a creation tool that may create default content blocks and accept nested parent structures.

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 a single, front-loaded sentence with no filler. Every word contributes to defining the tool's purpose, making it highly concise and easy to parse.

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

Completeness2/5

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

Despite the tool's complexity—six parameters, nested parent objects, content_type enum, and no output schema—the description provides only a high-level action. It does not explain required parameters, return behavior, or relationship to doc pages, so the agent is under-informed for correct invocation.

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%, and each parameter includes a descriptive explanation (e.g., parent id/type, content_type enum, create_default_content). The tool description adds no additional parameter meaning beyond the schema, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Create') and resource ('ClickUp Doc'), and clarifies the scope ('in a team/workspace'). This clearly distinguishes it from sibling tools like create_doc_page, update_doc, and delete_doc, which target a different aspect of the Docs API.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus related tools such as create_doc_page or update_doc. It does not mention prerequisites, alternatives, or exclusions, leaving the agent to infer usage from the name and schema alone.

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