ado-workflows-mcp

Overview Schema Source Related Servers Discussions Admin

create_pull_request

Create a pull request from a source branch to a target branch in Azure DevOps. Optionally add a title, description, draft mode, and link work items.

Instructions

Create a new pull request via the Azure DevOps SDK.

Constructs a PR from branch names with optional title, description, and draft mode.

Args: source_branch: Source branch name (with or without refs/heads/). target_branch: Target branch name. Defaults to "main". title: Optional PR title. description: Optional PR description. is_draft: Whether to create as a draft PR. working_directory: Optional path for context resolution. work_item_ids: Optional list of work item IDs to link to the PR.

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": {
      "source_branch": "<source_branch>"
    },
    "name": "create_pull_request"
  }
}

Input Schema

Name	Required	Default
`source_branch`	Yes
`target_branch`	No	main
`title`	No
`description`	No
`is_draft`	No
`working_directory`	No
`work_item_ids`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.12.0May 30, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. It lacks disclosure of side effects (e.g., triggers CI, permissions required) and only describes the creation action without deeper behavioral context.

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?

Well-structured with Args section and bullets. Not overly verbose, though the parameter list could be tightened slightly. Front-loading the main action is effective.

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?

Given 7 parameters and no annotations, the description covers parameters thoroughly. However, missing behavioral aspects like error conditions, required permissions, and side effects. Output schema exists, so return values are not needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the description adds meaningful context for each parameter: branch formats, defaults, optionality, and purpose (e.g., 'working_directory for context resolution', 'work_item_ids to link'). This compensates for the schema gap.

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 action ('Create a new pull request') and resource ('via Azure DevOps SDK'), with a brief summary of how it works. However, it does not differentiate from sibling tools like 'complete_pull_request' or 'update_pull_request'.

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. The description only states what it does, not when it should be chosen over other PR-related tools like 'update_pull_request' or 'complete_pull_request'.

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

Deploy Server