manage_pull_request_labelAdd or remove a label on an Azure DevOps pull request to organize or filter work. Specify the action, label, and confirm to update the PR.
Add or remove a pull request label.
| Name | Required | Description | Default |
|---|---|---|---|
| label | Yes | Label name for add, or label ID/name for remove. | |
| action | Yes | ||
| confirm | Yes | Must be true to perform the mutation. | |
| project | No | ||
| repositoryId | Yes | ||
| pullRequestId | Yes |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral disclosure burden. It only states the mutation action but does not mention side effects, idempotency, the required confirm flag, or failure behavior when a label does not exist.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The single sentence is efficient and front-loaded with the core operation, containing no filler. However, it is so terse that it omits necessary behavioral and usage context for a 6-parameter mutation tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations and no output schema, the description is the primary source of context, but it leaves out required confirmation behavior, parameter relationships, and usage routing. The schema partially compensates, but the overall definition is incomplete for safe invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 33%, and the description adds no parameter meaning beyond the 'add or remove' action already present in the action enum. It does not explain repositoryId, pullRequestId, project, or the label ID/name distinction for removal.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Add or remove') and resource ('pull request label'), making the tool's function unambiguous. It also distinguishes itself from the sibling list_pull_request_labels by clearly indicating this is a mutation rather than a read operation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given about when to use this tool versus alternatives such as list_pull_request_labels or manage_pull_request_reviewer. There are no conditions, exclusions, or context about whether labels should be checked first before adding or removing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.