ado-mcp

ado_deploy_release

Destructive

Initiate a release deployment to a specific environment/stage. Provide release and environment IDs.

Instructions

Trigger deployment of a release to an environment/stage. Destructive — initiates a deployment.

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": {
      "releaseId": "<releaseId>",
      "environmentId": "<environmentId>"
    },
    "name": "ado_deploy_release"
  }
}

Input Schema

Name	Required	Description
`comment`	No
`project`	No	Project name or ID (defaults to ADO_DEFAULT_PROJECT)
`releaseId`	Yes	Release ID
`environmentId`	Yes	Environment (stage) ID within the release

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already provide destructiveHint: true. The description reinforces this by stating 'Destructive — initiates a deployment,' which adds minimal clarity. However, it does not disclose other behaviors such as whether the deployment is asynchronous, potential side effects on the environment, or any permissions required. With annotations covering the destructive nature, the description provides adequate but not rich context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, consisting of two short sentences. Every word is purposeful and front-loaded with the core action. No superfluous information is present.

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 the destructive nature and lack of output schema, the description provides insufficient context. It does not explain what happens after triggering (e.g., returns a deployment ID?), error conditions, or the expected state changes. The agent lacks key information to safely invoke this tool.

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 75% (3 out of 4 parameters have descriptions). The description adds no parameter-specific information beyond what the schema provides. The baseline score is 3 for high coverage, and since the description does not enhance parameter understanding, it remains at 3.

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 clearly states the action (trigger deployment), the resource (a release), and the target (environment/stage). It distinguishes from sibling tools like ado_create_release (which creates a release definition) and ado_run_pipeline (pipeline deployment), as deploying a release is a distinct operation.

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 lacks explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., the release must already exist) or contrast with other deployment-related tools like ado_create_release or ado_run_pipeline. The usage context is implied but not clearly stated.

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

Deploy Server