Skip to main content
Glama
BlZvi
by BlZvi

Update Task

asana_update_task
Idempotent

Update an existing Asana task by modifying fields like name, notes, due date, assignee, or completion status. Provide only the fields to change and receive the updated task object.

Instructions

Update fields on an existing task. Only supply the fields you want to change. Returns the updated task object. To mark complete: set completed: true. To move sections: use asana_add_task_to_section instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew name for the task
notesNoNew description for the task
due_onNoNew due date in YYYY-MM-DD format
parentNoThe parent task ID to move this task under
task_idYesThe GID of the task to update (numeric string, e.g. `'19234567890123'`).
assigneeNoNew assignee (can be 'me' or a user ID)
completedNoMark task as completed or not
followersNoArray of user IDs to add as followers
html_notesNoHTML-like formatted description of the task. Does not support ALL HTML tags. Only a subset. The only allowed TAG in the HTML are: <body> <h1> <h2> <ol> <ul> <li> <strong> <em> <u> <s> <code> <pre> <blockquote> <a data-asana-type="" data-asana-gid=""> <hr> <img> <table> <tr> <td>. No other tags are allowed. Use the to create a newline. Do not use after <body>. Example: <body><h1>Motivation</h1> A customer called in to complain <h1>Goal</h1> Fix the problem</body>
custom_fieldsNoObject mapping custom field GID strings to their values. For enum fields use the enum option GID as the value.
resource_subtypeNoThe type of the task. Can be one of 'default_task' or 'milestone'
Behavior4/5

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

Discloses partial update semantics, return value ('Returns the updated task object'), and a shorthand for completion. Annotations already cover safety (readOnlyHint=false, destructiveHint=false, idempotentHint=true), and the description adds actionable context without contradicting them.

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 short, front-loaded sentences cover purpose, usage rule, return value, and key exceptions. Every sentence earns its place with no redundancy or fluff.

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 11 parameters and a nested object (custom_fields), the description sufficiently covers key behaviors: partial update, return value, completion, and section-moving exclusion. It does not explain permissions or all side effects, but schema and annotations fill most 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 coverage is 100%, so parameter descriptions already provide full semantics. The description only adds a note about the 'completed' parameter, which slightly reinforces schema info but does not deepen understanding of other parameters like custom_fields or html_notes.

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 fields on an existing task' with a specific verb and resource, distinguishing it from siblings like create_task and delete_task. The additional note about moving sections via asana_add_task_to_section clarifies scope.

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

Usage Guidelines5/5

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

Provides explicit usage instructions: 'Only supply the fields you want to change' and a specific how-to for completion ('set completed: true'). Also gives a clear alternative for moving sections, directing users to asana_add_task_to_section instead.

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/BlZvi/asana-mcp-server'

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