Skip to main content
Glama

update_work_item

Update fields on an existing Azure DevOps work item using its URL or numeric ID. Provide a dict of field reference names and new values.

Instructions

Update fields on an existing work item, addressed by URL or ID.

Accepts a dict of field reference names to values (e.g. {"System.State": "Closed", "System.IterationPath": "..."}).

Caveat — work board ≠ code repo: passing a bare numeric ID resolves the org/project from the cached repository context, which can land on the wrong organization when the work board lives in a different tenant than any of the discovered code repos. Prefer passing a full work-item URL whenever one is available — mutations in the wrong tenant are unrecoverable without manual intervention.

Args: work_item_url_or_id: A full Azure DevOps work-item URL or a numeric work-item ID. fields: Dict mapping field reference names to new values. working_directory: Optional path for repository-context resolution when using a numeric ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
work_item_url_or_idYes
fieldsYes
working_directoryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, but description discloses mutation behavior, the risk of wrong tenant, and the need for existing work item. Does not mention output schema behavior, but overall transparent about key traits.

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

Conciseness4/5

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

Well-structured with clear sections: purpose, caveat, args. Every sentence adds value. Slightly verbose with the example inline but still efficient.

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?

Covers inputs thoroughly but does not mention output format despite an output schema existing. Minor gap given complexity of tool and lack of schema descriptions.

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 has 0% description coverage; description compensates fully by explaining each parameter in detail, including types, purpose, and an example for the fields parameter. Adds significant value beyond schema.

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?

Clearly states 'Update fields on an existing work item' with specific verb and resource. Distinguishes from sibling tools like create_work_item, get_work_item, etc., by focusing on updating fields on an existing item.

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?

Provides explicit guidance to prefer URL over numeric ID due to cross-tenant risks. Includes a caveat about unrecoverable mutations. Could explicitly mention alternatives but sufficiently covers when and how to use.

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/grimlor/ado-workflows-mcp'

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