Skip to main content
Glama
84emllc

mcp-server-asana

by 84emllc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

asana_update_task

Modify an existing Asana task by updating its name, notes, due date, assignee, completion status, parent, followers, or custom fields using the task ID.

Instructions

Update an existing task's details

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 task ID to update
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 \n to create a newline. Do not use \n 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'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden for an 11-parameter mutation tool. It says nothing about partial-update semantics, permission requirements, side effects, reversibility, or what happens to omitted fields, leaving the agent with almost no behavioral context.

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?

The single sentence is front-loaded and contains no filler, but for a tool with 11 parameters and mutation semantics it is under-specified rather than appropriately concise. It omits information that would help an agent invoke the tool correctly.

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 the tool's complexity (11 parameters, nested custom_fields, no annotations, no output schema), the description is far too thin. It does not explain update scope, partial versus full replacement, permissions, or return behavior, so it is not complete enough for reliable invocation.

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%, and the schema itself gives detailed parameter descriptions (including the allowed HTML tag list for html_notes and custom_fields mapping behavior). The description adds no parameter meaning beyond 'details', so the baseline 3 is appropriate.

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 states the verb 'Update' and the resource 'task', so the core action is identifiable. However, 'details' is vague and it gives no indication of how it differs from related mutation siblings like asana_set_parent_for_task or asana_add_project_to_task, so it stops short of full sibling differentiation.

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?

There is no when-to-use guidance, no conditions for choosing this over asana_create_task or the specialized task-mutation siblings, and no mention of prerequisites such as required workspace/project permissions. The description merely restates the operation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools