Skip to main content
Glama

update_task

Update a task's title, description, status, assignees, and other fields in a workspace to keep project management accurate.

Instructions

Update a task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
SpaceNoOptional sub-space ID for further scoping inside the workspace.
extraNo
orderNoPass to reposition the task inside its status.
titleNo
statusNoMove task to a new status (on the same or different board).
task_idYesTask UUID or slug.
completeNoMarking a task complete is rejected if the task has incomplete blockers or a running timer.
due_dateNo
priorityNo
tags_addNoComposite field — tag names to add. Toolkit calls POST /tasks/{id}/tags/ with {"add": [...]} after the PATCH.
start_dateNo
descriptionNoPlain text task description. This is the field agents and CLI users should set. The toolkit converts it to a Quill Delta and writes `rich_description` automatically.
tags_removeNoComposite field — tag names to remove. Toolkit calls POST /tasks/{id}/tags/ with {"remove": [...]} after the PATCH.
OrganizationNoWorkspace (organization) ID the request is scoped to.
assignees_addNoInteger user IDs to add as assignees (get from listWorkspaceMembers). Toolkit calls POST /tasks/{id}/assignees/ with {"add": [...]} after the PATCH.
custom_fieldsNo
estimated_hoursNo
assignees_removeNoInteger user IDs to remove from assignees (get from listWorkspaceMembers). Toolkit calls POST /tasks/{id}/assignees/ with {"remove": [...]} after the PATCH.
rich_descriptionNoINTERNAL — Quill Delta representation. Set automatically by the toolkit when you pass `description`. Do not pass directly unless you have a pre-built Delta and know what you're doing.
Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It says nothing about mutation safety, side effects, or conditions (e.g., marking complete may fail if blockers exist). The parameter descriptions cover some behavior, but the main description is empty.

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

Conciseness2/5

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

While brief, the description is under-specified. It consists of one short sentence that adds no meaningful information, making it inadequate rather than concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 19 parameters, no output schema, and no annotations, the description is severely incomplete. Users (or agents) have no context about what fields can be updated, side effects, or how to use the tool effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 63% coverage with descriptions for many parameters. However, the tool description adds no value beyond what the schema already provides. For example, it doesn't explain that 'description' is converted to rich_description or that tags_add/remove are composite operations.

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 a task' is essentially a tautology of the tool name. It fails to specify which task fields can be updated or how this tool differs from sibling tools like update_task_assignees or update_task_tags.

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 on when to use this tool versus the many specialized task update tools (e.g., update_task_assignees, update_task_custom_fields). The description provides no 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/celeryhq/simplified-mcp-server'

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