mcp-for-azure-devops-boards

by danielealbano

Overview Schema Source Related Servers Discussions Admin

Rust

azdo_update_work_item

Update Azure DevOps work items by modifying fields such as state, title, description, tags, and priority.

Instructions

Update work item

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Work item ID to update
`tags`	No	Comma-separated tags (e.g., "bug, critical, ui")
`state`	No	State (New, Active, Resolved, Closed, etc.)
`title`	No	Work item title
`effort`	No	Effort estimate in hours
`fields`	No	Optional extra fields as JSON string (for custom fields)
`format`	No	Format for large text fields (description, acceptance criteria, repro steps, justification): "markdown" or "html" (default: "markdown")	markdown
`project`	Yes	AzDO project name
`activity`	No	Activity type (Development, Testing, Documentation, etc.)
`priority`	No	Priority (1-4, where 1 is highest)
`severity`	No	Severity for bugs (Critical, High, Medium, Low)
`area_path`	No	Area path (e.g., "MyProject\\Team1")
`board_row`	No	Board row/swimlane to place the work item in
`start_date`	No	Start date (YYYY-MM-DD)
`assigned_to`	No	User to assign the work item to (email or display name)
`description`	No	Work item description (use markdown syntax when format is "markdown", HTML tags when format is "html")
`repro_steps`	No	Reproduction steps (use markdown syntax when format is "markdown", HTML tags when format is "html")
`target_date`	No	Target/due date (YYYY-MM-DD)
`board_column`	No	Board column to place the work item in
`organization`	Yes	AzDO org name
`story_points`	No	Story points for estimation
`justification`	No	Justification (CMMI process template; use markdown syntax when format is "markdown", HTML tags when format is "html")
`iteration_path`	No	Iteration path (e.g., "MyProject\\Sprint 1")
`remaining_work`	No	Remaining work in hours
`acceptance_criteria`	No	Acceptance criteria (use markdown syntax when format is "markdown", HTML tags when format is "html")

Schema Changelog

Changes observed during successful MCP inspections.

Changed47 schema fields changedJul 13, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / acceptance_criteria / description

Previous value: -"Acceptance criteria (for user stories)"New value: +"Acceptance criteria (use markdown syntax when format is \"markdown\", HTML tags when format is \"html\")"

removedInput schema / properties / acceptance_criteria / nullable
```
Removed value: -true
```

changedInput schema / properties / acceptance_criteria / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

removedInput schema / properties / activity / nullable
```
Removed value: -true
```

changedInput schema / properties / activity / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

removedInput schema / properties / area_path / nullable
```
Removed value: -true
```

changedInput schema / properties / area_path / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

removedInput schema / properties / assigned_to / nullable
```
Removed value: -true
```

changedInput schema / properties / assigned_to / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

removedInput schema / properties / board_column / nullable
```
Removed value: -true
```

changedInput schema / properties / board_column / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

removedInput schema / properties / board_row / nullable
```
Removed value: -true
```

changedInput schema / properties / board_row / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedInput schema / properties / description / description

Previous value: -"Work item description (Basic HTML supported)"New value: +"Work item description (use markdown syntax when format is \"markdown\", HTML tags when format is \"html\")"

removedInput schema / properties / description / nullable
```
Removed value: -true
```

changedInput schema / properties / description / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

removedInput schema / properties / effort / nullable
```
Removed value: -true
```

changedInput schema / properties / effort / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

removedInput schema / properties / fields / nullable
```
Removed value: -true
```

changedInput schema / properties / fields / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

addedInput schema / properties / format

Added value: +{
+  "default": "markdown",
+  "description": "Format for large text fields (description, acceptance criteria, repro steps, justification): \"markdown\" or \"html\" (default: \"markdown\")",
+  "type": "string"
+}

removedInput schema / properties / iteration_path / nullable
```
Removed value: -true
```

changedInput schema / properties / iteration_path / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

addedInput schema / properties / justification

Added value: +{
+  "default": null,
+  "description": "Justification (CMMI process template; use markdown syntax when format is \"markdown\", HTML tags when format is \"html\")",
+  "type": [
+    "string",
+    "null"
+  ]
+}

removedInput schema / properties / priority / nullable
```
Removed value: -true
```

changedInput schema / properties / priority / type

Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]

removedInput schema / properties / remaining_work / nullable
```
Removed value: -true
```

changedInput schema / properties / remaining_work / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

changedInput schema / properties / repro_steps / description

Previous value: -"Reproduction steps (for bugs)"New value: +"Reproduction steps (use markdown syntax when format is \"markdown\", HTML tags when format is \"html\")"

removedInput schema / properties / repro_steps / nullable
```
Removed value: -true
```

changedInput schema / properties / repro_steps / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

removedInput schema / properties / severity / nullable
```
Removed value: -true
```

changedInput schema / properties / severity / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

removedInput schema / properties / start_date / nullable
```
Removed value: -true
```

changedInput schema / properties / start_date / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

removedInput schema / properties / state / nullable
```
Removed value: -true
```

changedInput schema / properties / state / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

removedInput schema / properties / story_points / nullable
```
Removed value: -true
```

changedInput schema / properties / story_points / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

removedInput schema / properties / tags / nullable
```
Removed value: -true
```

changedInput schema / properties / tags / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

removedInput schema / properties / target_date / nullable
```
Removed value: -true
```

changedInput schema / properties / target_date / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

removedInput schema / properties / title / nullable
```
Removed value: -true
```

changedInput schema / properties / title / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

removedInput schema / title
```
Removed value: -"UpdateWorkItemArgs"
```

Addedv1.0.0Jan 3, 2026

TDQS

C2.4/5.0

Behavior1/5

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

No annotations are present, and the description does not disclose any behavioral traits (e.g., idempotency, side effects, permissions, or rate limits). The agent receives no insight into how the tool behaves beyond the simple verb.

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 extremely short but lacks substance. It is nearly a tautology (restating the tool name). It could be expanded to include key details without becoming verbose.

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 (25 parameters, no output schema, no annotations), the one-line description is woefully inadequate. It omits prerequisites, return values, and behavioral context, leaving the agent underinformed.

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%, so each parameter is documented. The input schema fully describes the fields. The tool description adds no extra meaning beyond what the schema already provides, meeting the baseline.

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 'Update work item' clearly indicates a write operation on an existing work item, distinguishing it from create or query siblings. However, it lacks specificity on what aspects can be updated, which could be clearer.

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 is provided on when to use this tool versus alternatives like 'azdo_create_work_item' or 'azdo_link_work_items'. There are no context hints or exclusions.

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

azdo_update_work_item

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools