Skip to main content
Glama

update_task

Modify task properties, relationships, and status by dart_id. Use add_to/remove_from for incremental relationship updates and add an optional comment.

Instructions

Update a task. Pass dart_id and any fields to change at the top level. Supports add_to/remove_from for incremental relationship changes and optional comment. Relationship arrays use full replacement unless using add_to/remove_from.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dart_idYesTask dart_id (also accepts "id" or "task_id")
titleNoTask title (max 500 chars)
descriptionNoTask description (markdown supported)
dartboardNoDartboard dart_id or name
statusNoStatus dart_id or name
priorityNoPriority 1-5
sizeNoSize estimate 1-5
assigneesNoArray of assignee dart_ids, names, or emails
tagsNoArray of tag dart_ids or names
due_atNoDue date (ISO8601)
start_atNoStart date (ISO8601)
parent_taskNoParent task dart_id
subtask_idsNoIDs of subtask (child) tasks. Full replacement: set to [] to clear.
blocker_idsNoIDs of tasks that block this task. Full replacement: set to [] to clear.
blocking_idsNoIDs of tasks this task blocks. Full replacement: set to [] to clear.
duplicate_idsNoIDs of duplicate tasks. Full replacement: set to [] to clear.
related_idsNoIDs of related tasks. Full replacement: set to [] to clear.
commentNoOptional comment to add after updating (non-blocking)
add_toNoAppend IDs to relationship arrays. Fetches current values, merges, deduplicates. Keys: subtask_ids, blocker_ids, blocking_ids, duplicate_ids, related_ids
remove_fromNoRemove IDs from relationship arrays. Fetches current values, filters out specified IDs. Keys: subtask_ids, blocker_ids, blocking_ids, duplicate_ids, related_ids
Behavior4/5

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

No annotations provided, so description carries full burden. It explains behavior of relationship arrays (full replacement vs add_to/remove_from) and that comment is non-blocking. Lacks details on atomicity or side effects.

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?

Three concise sentences, front-loaded with main action, then key capabilities, then crucial behavioral detail. Every sentence adds value with no redundancy.

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 20 parameters and no output schema, description covers main behaviors well but omits what the API returns (e.g., updated task object). Still, it explains the critical relationship update modes.

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

Parameters5/5

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

Schema coverage is 100%, but description adds critical meaning: clarifies that relationship arrays use full replacement by default and how add_to/remove_from work (fetch, merge, deduplicate). This goes beyond schema explanations.

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 a task' with specific verb and resource. It distinguishes from siblings like create_task and batch_update_tasks by detailing incremental relationship changes and optional comment.

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

Usage Guidelines3/5

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

The description implies usage for updating tasks with two methods (full replacement vs incremental), but does not explicitly indicate when to use this tool over alternative tools like batch_update_tasks or when not to use it.

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/standardbeagle/dart-query'

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