Skip to main content
Glama
woodpecker-mcp

woodpecker-mcp

by si-essence

woodpecker_repos

Destructive

Manage Woodpecker CI repositories: list, inspect, activate, update, repair, delete, and view branches, pull requests, permissions, and workflows. Writes require confirm=true and writes enabled.

Instructions

Repository list, lookup, get, activate, update, repair, chown, delete, branches, pull requests, permissions, and workflows. Writes run only when confirm is true and WOODPECKER_ALLOW_WRITES=true. Actions: list, list_all, lookup, get, activate, update, repair, chown, delete, branches, pull_requests, permissions, workflows.

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": {
      "action": "<action>"
    },
    "name": "woodpecker_repos"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNo
nameNo
pageNo
actionYesWoodpecker operation to call.
branchNo
confirmNoBoolean true runs the write when WOODPECKER_ALLOW_WRITES is true. Omit it or pass false for a dry-run preview that sends nothing. The string true is rejected.
perPageNo
repo_idNo
documentNo
repo_full_nameNo
forge_remote_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

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

The description adds a genuine behavioral rule beyond the annotations: writes only execute when confirm is true AND WOODPECKER_ALLOW_WRITES=true. That is useful, but it partially duplicates the confirm parameter's own schema text, and it does not say which of the 13 actions are destructive, what delete or repair actually affect, or that omitted confirm yields a dry-run.

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

Conciseness3/5

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

Two sentences plus a redundant action enumeration that repeats the enum already present in the schema. The write-safety rule is placed second and the action list last, so the most decision-relevant constraint is not fully front-loaded.

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?

For a multiplexed tool with 11 parameters, nested document objects, no output schema, and destructive/open-world annotations, the description is far too thin. An agent cannot determine which parameters each action requires or what any action returns.

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

Parameters2/5

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

Schema description coverage is only 18% across 11 parameters, so the description must compensate and does not. It never clarifies the distinction between name, repo_id, repo_full_name, forge_remote_id, document, all, page, or perPage, and merely repeats the action enum values already declared in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates the operations ('list, lookup, get, activate, update, repair, chown, delete, branches, pull_requests, permissions, workflows') over the resource 'Repository', so the agent can tell this is the repo-management tool rather than cron/logs/pipelines/secrets/system. However, it is a bare noun list with no statement of what the tool actually does, and opaque actions like 'repair' and 'chown' are left undefined.

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?

There is no guidance on when to choose one action over another, no prerequisites, and no indication of which actions are read versus write other than the generic confirm gate. The only conditional given is the write-enablement rule, which is about execution safety rather than action selection.

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