Skip to main content
Glama

tasks_update

Update task properties such as subject, assignee, due date, or completion status. Changes apply immediately.

Instructions

Update an existing task.

Updates task properties such as subject, description, assignee, due date, or completion status.

Workflow tips:

  • Use tasks/list or tasks/get to find the task ID first

  • Only include fields you want to update

  • Set done = 1 to mark as completed

  • Changes take effect immediately

Common use cases:

  • Mark as done: { "id": 123, "done": 1 }

  • Reassign task: { "id": 123, "assignee_id": 456 }

  • Update due date: { "id": 123, "due_date": "2024-12-31" }

  • Update subject: { "id": 123, "subject": "Updated Task Title" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the task to update
subjectNoTask subject/title
project_idNoID of the project this task belongs to
assignee_idNoID of the user assigned to this task
parent_task_idNoID of the parent task if this is a subtask
doneNoWhether the task is done (0 = not done, 1 = done)
due_dateNoDue date in YYYY-MM-DD format
descriptionNoTask description
Behavior3/5

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

No annotations are provided, so the description carries the burden. It states 'Update an existing task' and 'Changes take effect immediately', which are clear for a mutation tool. It does not mention permissions, error handling, or side effects, but for a simple update tool, this is sufficient.

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 concise (~100 words) and well-structured. It starts with a clear purpose sentence, then lists the updatable properties, followed by workflow tips, and ends with common use cases with JSON examples. No redundant information.

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

Completeness4/5

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

Given there is no output schema, the description does not need to explain return values. It covers what the tool does, which parameters to use, and how to use them with examples. It could mention potential errors or limitations but is largely complete for an update tool.

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

Parameters4/5

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

Schema coverage is 100% with descriptions for all 8 parameters. The description adds value beyond the schema by providing concrete use case examples (e.g., marking a task as done, reassigning, updating due date) that illustrate how parameters are used together and the expected format (e.g., 'done': 1, 'due_date': 'YYYY-MM-DD').

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 clearly states 'Update an existing task' and lists specific properties that can be updated (subject, description, assignee, due date, completion status). It distinguishes from sibling tools like tasks_create, tasks_delete, tasks_get, and tasks_list by focusing on updating an existing task.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Workflow tips are provided: use tasks/list or tasks/get to find the task ID first, only include fields to update, set done=1 to mark completed, and changes take effect immediately. Common use cases with JSON examples further guide usage. However, it does not explicitly state when not to use or alternatives to exclude.

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/iamsamuelfraga/mcp-pipedrive'

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