Skip to main content
Glama
Tiberriver256

Azure DevOps MCP Server

create_work_item

Creates a new Azure DevOps work item with required type and title, and optional fields for assignee, priority, tags, area, iteration, parent link, and HTML description.

Instructions

Create a new work item

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTags to add to the work item
titleYesThe title of the work item
areaPathNoThe area path for the work item
parentIdNoThe ID of the parent work item to create a relationship with
priorityNoThe priority of the work item
projectIdNoThe ID or name of the project (Default: MyProject)
assignedToNoThe email or name of the user to assign the work item to
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.
workItemTypeYesThe type of work item to create (e.g., "Task", "Bug", "User Story")
iterationPathNoThe iteration path for the work item
organizationIdNoThe ID or name of the organization (Default: mycompany)
additionalFieldsNoAdditional fields to set 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 provided. The description only says 'Create a new work item' and does not disclose behavioral traits such as permissions, idempotency, or side effects.

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 sentence, which is concise but lacks structure. It is front-loaded but does not provide additional details beyond the bare minimum.

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?

With 12 parameters, no output schema, and no annotations, the description is insufficient. It does not explain return values, error conditions, or when to use the tool, leaving the agent under-informed.

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 all 12 parameters are already described in the schema. The tool description adds no extra meaning beyond the schema, 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 states 'Create a new work item', which is a specific verb and resource. It clearly indicates the action, but does not differentiate from sibling tools like 'update_work_item' or 'manage_work_item_link'.

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. There are multiple work-item-related siblings (e.g., update_work_item, manage_work_item_link), and the description provides no context for selection.

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