Skip to main content
Glama
DiversioTeam

ClickUp MCP Server

by DiversioTeam

assign_task

Assign users to tasks in ClickUp by specifying task IDs and user IDs to manage team responsibilities and project workflows.

Instructions

Assign users to a task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesTask ID
user_idsYesUser IDs to assign

Implementation Reference

  • The primary handler for the 'assign_task' MCP tool. Resolves flexible task_id formats, updates assignees via ClickUp API, handles errors, and returns formatted response.
    async def assign_task(self, task_id: str, user_ids: List[int]) -> Dict[str, Any]:
        """Assign users to task."""
        try:
            # First resolve the task to get the internal ID
            resolved_task = await self._resolve_task_id(task_id)
            update_request = UpdateTaskRequest(assignees={"add": user_ids})
            task = await self.client.update_task(resolved_task.id, update_request)
        except ClickUpAPIError as e:
            return {"error": f"Failed to assign users to task '{task_id}': {e!s}"}
    
        return {
            "task_id": task.id,
            "assignees": [u.username for u in task.assignees],
            "updated": True,
        }
  • JSON schema defining the input parameters and validation for the assign_task tool.
    Tool(
        name="assign_task",
        description="Assign users to a task",
        inputSchema={
            "type": "object",
            "properties": {
                "task_id": {"type": "string", "description": "Task ID"},
                "user_ids": {
                    "type": "array",
                    "items": {"type": "integer"},
                    "description": "User IDs to assign",
                },
            },
            "required": ["task_id", "user_ids"],
        },
    ),
  • Maps the 'assign_task' tool name to its handler function in the internal dispatch dictionary used by call_tool().
    "get_assignees": self.get_assignees,
    "assign_task": self.assign_task,
    "list_spaces": self.list_spaces,
  • MCP server handler that exposes the assign_task tool schema (via get_tool_definitions()) to clients.
    @self.server.list_tools()
    async def list_tools() -> List[Tool]:
        """List all available tools."""
        return self.tools.get_tool_definitions()
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. It implies a mutation ('assign') but doesn't specify permissions required, whether assignments are additive or replace existing ones, error handling (e.g., invalid user IDs), or side effects. This is inadequate for a mutation tool with zero annotation coverage.

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 with zero waste. It's front-loaded and appropriately sized for the tool's complexity, making it easy to parse quickly.

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?

Given this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., permissions, idempotency), output format, or error cases, which are critical for safe and effective use. The high schema coverage doesn't compensate for these gaps.

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 both parameters ('task_id' and 'user_ids') adequately. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints (e.g., user IDs must be valid). Baseline 3 is appropriate when schema does the heavy lifting.

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 verb ('assign') and resource ('users to a task'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_assignees' (which retrieves assignees) or 'update_task' (which might include assignment), so it lacks sibling distinction.

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., task must exist), exclusions (e.g., cannot assign to completed tasks), or comparisons to siblings like 'update_task' or 'bulk_update_tasks', leaving the agent to infer usage context.

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