Skip to main content
Glama
Sign In
ClickUp MCP Server

ClickUp MCP Server

by azukhrufy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

update_doc_page

Update a page in a ClickUp Doc by specifying its new name and content, along with the required team, doc, and page IDs.

Instructions

Update a page within a ClickUp Doc.

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>",
      "doc_id": "<doc_id>",
      "page_id": "<page_id>"
    },
    "name": "update_doc_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew name of the page
doc_idYesThe ID of the doc
contentNoNew content of the page
page_idYesThe ID of the page
team_idYesThe ID of the team (workspace)
content_typeNoContent type

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, the description carries the full burden of behavioral disclosure. It only says 'update' without mentioning whether updates are partial or full replacements, if special permissions are required, or what side effects occur. This is a significant gap for a mutation tool.

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 concise sentence that directly states the action. It is front-loaded and contains no unnecessary wording.

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?

For a mutation tool with 6 parameters and no output schema, this description is too thin. It does not explain the update semantics (e.g., whether content replaces existing content), how content_type affects behavior, or what the response contains. The absence of this context makes it incomplete for effective tool selection and 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?

The schema descriptions cover 100% of the 6 parameters, so the description does not need to repeat them. The schema already explains team_id, doc_id, page_id, name, content, and content_type. The description adds no additional parameter-level context, but the schema is sufficient.

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 'Update a page within a ClickUp Doc' uses a specific verb and resource, clearly distinguishing it from sibling tools like create_doc_page and delete_doc_page. It is unambiguous about the tool's primary function.

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?

No guidance is provided on when to use this tool versus alternatives such as create_doc_page or update_doc. There are no prerequisites, exclusions, or context about typical use cases.

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