Skip to main content
Glama

manage_pipelines

List, retrieve, and trigger Azure DevOps pipelines; fetch logs, build changes, variable groups, and environments to monitor and control CI/CD workflows.

Instructions

Manage Azure DevOps CI/CD pipelines. Actions: 'list', 'get', 'list_runs', 'get_run', 'get_logs', 'get_log', 'get_build_changes', 'list_definitions', 'list_variable_groups', 'get_variable_group', 'list_environments', 'trigger'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: 'list', 'get', 'list_runs', 'get_run', 'trigger', 'get_logs', 'get_log', 'get_build_changes', 'list_definitions', 'list_variable_groups', 'get_variable_group', 'list_environments'
project_keyNoProject name (required)
pipeline_idNoPipeline ID (required for get, list_runs, trigger, get_logs, get_log)
run_idNoRun ID (required for get_run, get_logs, get_log)
log_idNoLog ID (required for get_log)
build_idNoBuild ID (required for get_build_changes)
branchNoBranch name to run pipeline on (for trigger)
topNoMax results to return
group_idNoVariable group ID (required for get_variable_group)
Behavior2/5

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

With no annotations, the description bears full responsibility for disclosing behavioral traits. It only lists action names, which imply operations but do not explain side effects, permissions required, or consequences (e.g., triggering a pipeline may start a build). Minimal behavioral context is provided.

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?

The description is concise, using a single sentence to list actions after stating the resource. It is front-loaded and efficient, though it could be improved by grouping related actions or adding more structure.

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 tool's complexity (9 parameters, multiple actions, no output schema), the description is incomplete. It lacks information about return values, error conditions, or what each action accomplishes beyond the action name. The schema provides parameter details, but the description does not provide the high-level context needed for effective tool selection.

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?

The input schema covers all parameters with descriptions (100% coverage), so the baseline is 3. The tool description adds no extra parameter context beyond the schema, merely listing actions. It does not enhance understanding of parameter values or constraints.

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 tool manages Azure DevOps CI/CD pipelines and lists specific actions, distinguishing it from sibling tools that manage other resources. However, the verb 'Manage' is generic and the description is a list without a clear statement of the tool's overall purpose.

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 guidelines are provided about when to use this tool versus alternatives or when to use specific actions. The description simply enumerates actions without context about prerequisites, typical use cases, or when not to use the tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zach-snell/adtk'

If you have feedback or need assistance with the MCP directory API, please join our Discord server