Skip to main content
Glama
Leanware-io

ClickUp MCP Integration

by Leanware-io

clickup_edit_page

Modify ClickUp document pages by updating name, subtitle, or markdown content using replace, append, or prepend modes.

Instructions

Edit a page in a ClickUp doc

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doc_idYesClickUp doc ID
page_idYesClickUp page ID
nameNoPage name
sub_titleNoPage subtitle
contentNoPage content in markdown format
content_edit_modeNoContent edit mode (replace, append, prepend), default is replace

Implementation Reference

  • Full tool definition for 'clickup_edit_page', including Zod input schema, description, and handler function that prepares parameters and calls the docsService.editPage method.
    const editPageTool = defineTool((z) => ({
      name: "clickup_edit_page",
      description: "Edit a page in a ClickUp doc",
      inputSchema: {
        doc_id: z.string().describe("ClickUp doc ID"),
        page_id: z.string().describe("ClickUp page ID"),
        name: z.string().optional().describe("Page name"),
        sub_title: z.string().optional().describe("Page subtitle"),
        content: z.string().optional().describe("Page content in markdown format"),
        content_edit_mode: z
          .string()
          .optional()
          .describe(
            "Content edit mode (replace, append, prepend), default is replace"
          ),
      },
      handler: async (input) => {
        const pageParams: EditPageParams = {
          docId: input.doc_id,
          pageId: input.page_id,
          name: input.name,
          sub_title: input.sub_title,
          content: input.content,
          content_edit_mode: input.content_edit_mode,
        };
        const response = await docsService.editPage(pageParams);
        return {
          content: [{ type: "text", text: JSON.stringify(response) }],
        };
      },
    }));
  • Helper method in DocsService that performs the actual API call to edit a ClickUp doc page using PUT request with prepared payload.
    async editPage(params: EditPageParams): Promise<ClickUpDocPage> {
      const { docId, pageId, name, sub_title, content, content_edit_mode } =
        params;
      const pageData = {
        name,
        sub_title,
        content,
        content_edit_mode: content_edit_mode || "replace",
        content_format: "text/md",
      };
    
      return this.request<ClickUpDocPage>(
        `/${this.workspaceId}/docs/${docId}/pages/${pageId}`,
        {
          method: "PUT",
          body: JSON.stringify(pageData),
        }
      );
    }
  • src/index.ts:89-91 (registration)
    Registers all imported tools, including clickup_edit_page, into the MCP server by iterating over the tools array and calling server.tool().
    tools.forEach((tool) => {
      server.tool(tool.name, tool.description, tool.inputSchema, tool.handler);
    });
  • src/index.ts:17-17 (registration)
    Imports the clickup_edit_page tool from docs.controller.ts
    editPageTool,
  • TypeScript interface defining the parameters for editing a page, used in the service and controller.
    export interface EditPageParams {
      docId: string;
      pageId: string;
      name?: string;
      sub_title?: string;
      content?: string;
      content_edit_mode?: string;
    }
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 behavioral disclosure. It states 'Edit a page' which implies a mutation operation, but fails to describe critical behaviors: whether this requires specific permissions, if edits are reversible, potential side effects (e.g., versioning), rate limits, or what the response looks like (no output schema). This leaves significant gaps 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, efficient sentence that states the core functionality without unnecessary words. It's appropriately sized for the tool's complexity and front-loads the essential information ('Edit a page in a ClickUp doc'). Every word earns its place.

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, no annotations, and no output schema, the description is incomplete. It lacks behavioral context (permissions, side effects), usage guidelines, and any information about return values or error conditions. While the schema covers parameters well, the overall context for safe and effective tool invocation is insufficient.

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 input schema has 100% description coverage, providing clear documentation for all 6 parameters including their types and purposes. The description adds no additional parameter semantics beyond what's already in the schema (e.g., it doesn't explain format requirements for 'content' or clarify the relationship between 'doc_id' and 'page_id'). The baseline score of 3 reflects adequate but minimal value addition.

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 clearly states the action ('Edit') and resource ('a page in a ClickUp doc'), making the purpose immediately understandable. It distinguishes itself from siblings like 'clickup_create_page' (creation vs. editing) and 'clickup_get_page' (reading vs. editing), though it doesn't explicitly mention these distinctions in the description itself.

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 alternatives. It doesn't mention prerequisites (e.g., needing an existing page), exclusions, or comparisons with sibling tools like 'clickup_update_task' (for tasks vs. pages) or 'clickup_create_page' (for new pages vs. editing existing ones).

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/Leanware-io/clickup-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server