Skip to main content
Glama
DiversioTeam

ClickUp MCP Server

by DiversioTeam

update_task

Modify ClickUp task details including title, description, status, priority, due date, and assignees to keep project information current.

Instructions

Update task properties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesTask ID
titleNoNew title
descriptionNoNew description
statusNoNew status
priorityNoNew priority
due_dateNoNew due date
assignees_addNoUser IDs to add as assignees
assignees_removeNoUser IDs to remove as assignees

Implementation Reference

  • The primary handler function for the MCP 'update_task' tool. Resolves task ID using _resolve_task_id, constructs UpdateTaskRequest from parameters, calls client.update_task, and returns formatted result.
    async def update_task(
        self,
        task_id: str,
        title: Optional[str] = None,
        description: Optional[str] = None,
        status: Optional[str] = None,
        priority: Optional[int] = None,
        due_date: Optional[str] = None,
        assignees_add: Optional[List[int]] = None,
        assignees_remove: Optional[List[int]] = None,
        **kwargs: Any,
    ) -> Dict[str, Any]:
        """Update task properties."""
        try:
            # First resolve the task to get the internal ID
            resolved_task = await self._resolve_task_id(task_id)
            parsed_id = resolved_task.id
        except ClickUpAPIError as e:
            return {"error": f"Failed to resolve task '{task_id}': {e!s}"}
    
        update_request = UpdateTaskRequest()
    
        if title:
            update_request.name = title
        if description is not None:
            update_request.description = description
        if status:
            update_request.status = status
        if priority:
            update_request.priority = priority
        if due_date:
            dt = datetime.fromisoformat(due_date.replace("Z", "+00:00"))
            update_request.due_date = int(dt.timestamp() * 1000)
            update_request.due_date_time = True
    
        if assignees_add or assignees_remove:
            update_request.assignees = {}
            if assignees_add:
                update_request.assignees["add"] = assignees_add
            if assignees_remove:
                update_request.assignees["rem"] = assignees_remove
    
        task = await self.client.update_task(parsed_id, update_request)
    
        return {
            "id": task.id,
            "name": task.name,
            "status": task.status.status,
            "updated": True,
        }
  • JSON schema definition for the 'update_task' tool input parameters, defined in ClickUpTools.get_tool_definitions().
    Tool(
        name="update_task",
        description="Update task properties",
        inputSchema={
            "type": "object",
            "properties": {
                "task_id": {"type": "string", "description": "Task ID"},
                "title": {"type": "string", "description": "New title"},
                "description": {"type": "string", "description": "New description"},
                "status": {"type": "string", "description": "New status"},
                "priority": {"type": "integer", "description": "New priority"},
                "due_date": {"type": "string", "description": "New due date"},
                "assignees_add": {
                    "type": "array",
                    "items": {"type": "integer"},
                    "description": "User IDs to add as assignees",
                },
                "assignees_remove": {
                    "type": "array",
                    "items": {"type": "integer"},
                    "description": "User IDs to remove as assignees",
                },
            },
            "required": ["task_id"],
        },
    ),
  • Registration of the 'update_task' handler (and all other tools) in the ClickUpTools._tools dictionary during __init__, used by call_tool.
    self._tools: Dict[str, Callable] = {
        "create_task": self.create_task,
        "get_task": self.get_task,
        "update_task": self.update_task,
        "delete_task": self.delete_task,
        "list_tasks": self.list_tasks,
        "search_tasks": self.search_tasks,
        "get_subtasks": self.get_subtasks,
        "get_task_comments": self.get_task_comments,
        "create_task_comment": self.create_task_comment,
        "get_task_status": self.get_task_status,
        "update_task_status": self.update_task_status,
        "get_assignees": self.get_assignees,
        "assign_task": self.assign_task,
        "list_spaces": self.list_spaces,
        "list_folders": self.list_folders,
        "list_lists": self.list_lists,
        "find_list_by_name": self.find_list_by_name,
        # Bulk operations
        "bulk_update_tasks": self.bulk_update_tasks,
        "bulk_move_tasks": self.bulk_move_tasks,
        # Time tracking
        "get_time_tracked": self.get_time_tracked,
        "log_time": self.log_time,
        # Templates
        "create_task_from_template": self.create_task_from_template,
        "create_task_chain": self.create_task_chain,
        # Analytics
        "get_team_workload": self.get_team_workload,
        "get_task_analytics": self.get_task_analytics,
        # User management
        "list_users": self.list_users,
        "get_current_user": self.get_current_user,
        "find_user_by_name": self.find_user_by_name,
    }
  • MCP server handler for listing tools, which returns definitions including 'update_task' schema from ClickUpTools.get_tool_definitions().
    @self.server.list_tools()
    async def list_tools() -> List[Tool]:
        """List all available tools."""
        return self.tools.get_tool_definitions()
  • ClickUpClient.update_task method: performs the actual API PUT request to /task/{task_id} with UpdateTaskRequest data, used by the tool handler.
    async def update_task(
        self,
        task_id: str,
        updates: UpdateTaskRequest,
    ) -> Task:
        """Update a task."""
        data = await self._request(
            "PUT",
            f"/task/{task_id}",
            json=updates.model_dump(exclude_none=True),
        )
        return Task(**data)
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Update task properties' implies a mutation operation but provides no information about permissions required, whether changes are reversible, what happens to unspecified properties, error conditions, or response format. For a mutation tool with zero annotation coverage, this is insufficient.

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?

The description is extremely concise with just three words, which is efficient and front-loaded. However, it's arguably too brief given the tool's complexity and the lack of annotations, bordering on under-specification rather than optimal conciseness.

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 8 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what happens during updates, what permissions are needed, how errors are handled, or what the tool returns. The description should provide more context given the tool's complexity and the absence of structured metadata.

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%, with all 8 parameters well-documented in the schema itself. The description adds no additional parameter information beyond what's already in the structured schema. With complete schema coverage, the baseline score of 3 is appropriate since the description doesn't need to compensate for schema gaps.

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

Purpose2/5

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

The description 'Update task properties' is a tautology that essentially restates the tool name 'update_task' without providing meaningful context. It doesn't specify what kind of properties can be updated or distinguish this tool from sibling tools like 'bulk_update_tasks' or 'update_task_status'.

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

Usage Guidelines1/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. With multiple sibling tools like 'bulk_update_tasks', 'update_task_status', and 'assign_task' that handle related operations, there's no indication of when this specific single-task update tool is appropriate versus those alternatives.

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/DiversioTeam/clickup-mcp'

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