Skip to main content
Glama

update_task

Idempotent

Update task metadata by specifying the task ID and optional new values for name, status, priority, milestone, description, or flow IDs.

Instructions

Update task metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTask ID
nameNoNew name (NULL = don't update)
milestone_idNoNew milestone ID (NULL = don't update)
statusNo'pending', 'in_progress', 'completed', 'blocked' (NULL = don't update)
descriptionNoNew description (NULL = don't update)
flow_idsNoArray of flow IDs [1, 3, 5] (NULL = don't update)
priorityNo'low', 'medium', 'high', 'critical' (NULL = don't update)
Behavior3/5

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

Annotations already declare idempotentHint=true and non-destructive nature. The description adds no additional behavioral details (e.g., side effects, permissions, response format). It is consistent with annotations but does not augment them.

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

Conciseness3/5

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

The description is a single short sentence, which is concise but lacks front-loaded key details. It is not wasteful, but the brevity omits useful context that could aid the agent.

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

Completeness2/5

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

Given the lack of output schema and the large set of sibling tools, the description fails to provide complete context. It does not mention return values, error conditions, or how it relates to other update tools.

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?

Input schema covers all 7 parameters with descriptions (100% coverage). The description adds no per-parameter meaning beyond the schema, meeting the baseline but not compensating for any gaps.

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 'Update task metadata' which clearly identifies the operation and resource. However, it does not differentiate from other update tools like update_subtask or update_milestone, missing an opportunity to specify the unique scope.

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 alternatives. No prerequisites, when-not-to-use, or related tool suggestions are provided, leaving the agent without decision 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/aryanduntley/aimfp'

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