Skip to main content
Glama
rafadepaula

@rafadepaula/clickup-mcp

by rafadepaula
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

clickup_create_document_page

Create a new page inside a ClickUp document, with a name, content, optional subtitle, and parent page for sub-pages. Use it to add and organize documentation content directly in ClickUp.

Instructions

Create a new page in a ClickUp document.

Input Schema

NameRequiredDescriptionDefault
nameYesName and title of the page
contentYesContent of the page
sub_titleNoSubtitle of the page
document_idYesID of the document to create the page in (e.g. 'ad-909705'). In ClickUp doc URLs, 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_formatNoThe format of the page contenttext/md
parent_page_idNoID of the parent page (if this is a sub-page)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: it doesn't say the operation mutates persistent state, whether it requires write permissions, whether a created page can be deleted, or what is returned. For a creation/mutation tool with zero annotation coverage this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, but the terseness is under-specification rather than disciplined concision given the tool's complexity.

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?

With 7 parameters, a mutation side effect, no annotations, and no output schema, the description should at minimum cover the write semantics and the parent/sub-page behavior. It covers none of these, leaving the agent reliant entirely on the schema.

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 the schema already documents document_id (including URL parsing), workspace_id, content_format enum, and parent_page_id. The description adds no parameter meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Create a new page in a ClickUp document'), which is clearly distinguishable from clickup_create_document and clickup_update_document_page. However, it never explicitly names those siblings or states the relationship, so it stops short of full differentiation.

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?

There is no guidance on when to use this versus clickup_create_document or clickup_update_document_page, nor any mention of prerequisites such as needing an existing document_id or how sub-pages differ from top-level pages. The agent must infer all of this.

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