ado-search-mcp

Overview Schema Source Related Servers Discussions Admin

ado_create

Create new Azure DevOps work items—bugs, user stories, tasks, epics, features—by specifying a title and type, with optional fields for details.

Instructions

Create a new work item in Azure DevOps

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>",
      "title": "<title>"
    },
    "name": "ado_create"
  }
}

Input Schema

Name	Required	Description
`area`	No	Area path
`tags`	No	Semicolon-separated tags
`type`	Yes	Work item type (Bug, User Story, Task, Epic, Feature)
`state`	No	Initial state
`title`	Yes	Work item title
`fields`	No	Additional ADO fields as key-value pairs
`parent`	No	Parent work item ID
`reason`	No	Reason (e.g. for closing)
`priority`	No	Priority (1=highest)
`iteration`	No	Iteration path
`assigned_to`	No	Assignee email or display name
`description`	No	Description (HTML)
`story_points`	No	Story points
`acceptance_criteria`	No	Acceptance criteria (HTML)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It identifies the operation as creating a work item, implying a mutation, but doesn't disclose side effects, required team/project context, validation rules, or what happens on creation. It gives basic transparency but lacks behavioral depth.

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?

A single, clear sentence that is efficient. It could potentially add usage/behavior details, but as written it has no waste and the core purpose is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is minimal but combined with a 100%-covered schema it is adequate. Missing elements include explicit mutation warning given no annotations, and guidance about which ADO project/organization context applies, but the core creation purpose is complete enough.

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 documents every parameter. The description ('Create a new work item') adds no additional parameter semantics beyond what the schema already provides, but because coverage is complete the baseline of 3 applies.

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 a specific verb ('Create') and resource ('work item in Azure DevOps'). It is distinct enough from siblings like ado_update or ado_fetch, though it doesn't name any sibling differences.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by describing the creation action, but provides no explicit guidance about when to choose this tool over alternatives such as ado_update or ado_add_link. With many siblings, some distinction would elevate it.

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

Deploy Server