Skip to main content
Glama
Tiberriver256

Azure DevOps MCP Server

update_work_item

Modify an existing Azure DevOps work item: change title, state, priority, assignment, tags, area/iteration path, or description. Supports adding/removing tags and custom fields.

Instructions

Update an existing work item

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoOverwrite/set the complete set of tags
stateNoThe updated state of the work item
titleNoThe updated title of the work item
areaPathNoThe updated area path for the work item
priorityNoThe updated priority of the work item
tagsToAddNoList of tags to append to the work item
assignedToNoThe email or name of the user to assign the work item to
workItemIdYesThe ID of the work item to update
descriptionNoWork item description in HTML format. Multi-line text fields (i.e., System.History, AcceptanceCriteria, etc.) must use HTML format. Do not use CDATA tags.
tagsToRemoveNoList of tags to remove from the work item
iterationPathNoThe updated iteration path for the work item
additionalFieldsNoAdditional fields to update on the work item. Multi-line text fields (i.e., System.History, AcceptanceCriteria, etc.) must use HTML format. Do not use CDATA tags.
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It does not disclose any behavioral aspects such as whether updates are partial or full overwrites, required permissions, or side effects. For a tool with 12 parameters, this is insufficient.

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 description is very concise (one sentence) but lacks important details about behavior and usage. It is under-specified, not efficiently compact.

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 12 parameters, no output schema, and no annotations, the description is inadequate. It does not explain how parameters interact (e.g., tags overwrite vs. tagsToAdd/Remove) or what the response looks like.

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% with descriptions for all parameters. The tool description adds no extra meaning beyond what the schema already provides. Baseline score of 3 is appropriate.

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 states 'Update an existing work item', which clearly identifies the action (update) and the resource (work item). It distinguishes from sibling tools like create_work_item and list_work_items.

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, and no mention of when not to use it. The description provides no usage 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/Tiberriver256/mcp-server-azure-devops'

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