Retrieve variables from Azure DevOps build or release pipelines. Specify project and optional pipeline name to get configuration values for automation or troubleshooting.
Get pipeline variables from build/release pipelines
| Name | Required | Description | Default |
|---|---|---|---|
| project | Yes | Project name | |
| pipelineName | No | Pipeline name (optional - will list all if not provided) | |
| pipelineType | No | Pipeline type: build or release |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action and resource but does not disclose what happens when pipelineName is omitted, whether the tool returns all variables, or any permission/read-only guarantees. The description adds minimal behavioral context beyond the basic operation.
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 description is a single short sentence with no filler. The verb and object are front-loaded, and the source scope is expressed efficiently. Every word contributes meaning, making it appropriately concise.
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?
For a simple read-only getter with fully described parameters, the description is adequate but thin. It does not explicitly mention that omitting pipelineName lists all pipelines, nor does it describe the return value shape. Since there is no output schema, some important contextual details rely on the input schema or inference.
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 100%, so the baseline is 3. The description does not add meaning beyond the schema—it only paraphrases the pipelineType enum by saying 'build/release pipelines'. No additional insight into project or pipelineName semantics is provided.
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 ('Get') and resource ('pipeline variables') and scopes it to 'build/release pipelines'. This clearly distinguishes it from siblings like get_variable_groups or repository tools. The purpose is immediately recognizable and unambiguous.
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?
There is no guidance on when to use this tool versus alternatives such as get_variable_groups. The description does not state any decision rules, exclusions, or context for choosing this tool. The 'build/release pipelines' scope is implied rather than explicitly positioned against sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.