Skip to main content
Glama

manage_work_items

Manage Azure DevOps work items including tasks, bugs, and user stories. Perform actions like create, update, delete, link items, add comments, and track changes.

Instructions

Manage Azure DevOps work items (tasks, bugs, user stories, epics). Actions: 'get', 'batch_get', 'list_types', 'get_links', 'get_history', 'list_comments', 'my_items', 'iteration_items', 'create', 'update', 'delete', 'add_comment', 'batch_update', 'add_children', 'link', 'unlink', 'add_artifact_link', 'update_comment'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: 'get', 'create', 'update', 'delete', 'add_comment', 'list_comments', 'get_links', 'list_types', 'get_history', 'batch_get', 'batch_update', 'add_children', 'link', 'unlink', 'add_artifact_link', 'my_items', 'iteration_items', 'update_comment'
project_keyNoProject name (required for most actions)
work_item_idNoWork item ID (required for get, update, delete, add_comment, list_comments, get_links, get_history)
work_item_idsNoWork item IDs (for batch_get, max 200)
work_item_typeNoWork item type: Task, Bug, User Story, Epic, Feature, Issue (required for create)
titleNoWork item title (required for create)
descriptionNoWork item description in HTML (for create, update)
stateNoWork item state: New, Active, Closed, etc. (for update)
assigned_toNoAssignee display name or email (for create, update)
area_pathNoArea path e.g. Project\Team (for create, update)
iteration_pathNoIteration path e.g. Project\Sprint 1 (for create, update)
priorityNoPriority: 1=Critical, 2=High, 3=Medium, 4=Low (for create, update)
parent_idNoParent work item ID to link (for create, add_children)
tagsNoSemicolon-separated tags (for create, update)
commentNoComment text in HTML (for add_comment, update_comment, add_artifact_link)
comment_idNoComment ID (required for update_comment)
queryNoWIQL query string (for 'list' action via WIQL)
fieldsNoFields to return (for batch_get). Default: System.Title, System.State, System.AssignedTo
topNoMax results to return (for WIQL queries)
target_idNoTarget work item ID (required for link)
link_typeNoLink type name (for link, add_artifact_link), e.g. System.LinkTypes.Related, System.LinkTypes.Hierarchy-Forward
relation_indexNoRelation index to remove (required for unlink)
artifact_uriNoArtifact URI for artifact links (required for add_artifact_link), e.g. vstfs:///Git/Commit/{projectId}%2F{repoId}%2F{commitId}
titlesNoList of titles for child work items (required for add_children)
teamNoTeam name (optional, scopes iteration_items to a specific team)
iteration_idNoIteration ID (required for iteration_items)
include_completedNoInclude completed/closed work items (for my_items, default false)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it lists actions, it doesn't explain permissions needed, rate limits, side effects, or response formats. For a tool with 19 actions including destructive operations like 'delete', this leaves critical behavioral information unspecified.

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 run-on sentence listing 19 actions without prioritization or grouping. While it's information-dense, the structure could be improved with categorization (e.g., grouping read vs. write actions). Every action listed earns its place, but the presentation lacks organization.

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?

For a complex tool with 19 actions, 27 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain the relationship between actions, doesn't provide examples, and doesn't cover error conditions or response formats. The agent would struggle to use this tool effectively without trial and error.

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 the schema fully documents all 27 parameters. The description adds no parameter-specific information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 clearly states the tool manages Azure DevOps work items and lists 19 specific actions, providing a comprehensive overview of functionality. However, it doesn't distinguish this tool from sibling tools like manage_boards or manage_projects, which might have overlapping domains in Azure DevOps.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when to choose specific actions, or how this tool relates to sibling tools like manage_boards or manage_projects. The agent must infer usage from the action list alone.

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/zach-snell/adtk'

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