Skip to main content
Glama
RikiGomes

woodpecker-mcp

by RikiGomes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List repositories

list_repos
Read-only

Lists Woodpecker CI repositories visible to the instance token so you can discover repo slugs; returns key fields and supports active-only or name filters.

Instructions

Lists repositories the instance's token can see, returning id, full_name, default_branch, active and forge_url for each. Active repositories only unless all is true; name keeps only repositories whose owner/name contains it (case-insensitive). The list comes back in a single response (this tool takes no paging parameters). Use it to discover repositories; it isn't needed when you already know the "owner/name" slug, since the other tools accept slugs directly.

Input Schema

NameRequiredDescriptionDefault
allNoInclude inactive repositories (default: active only).
nameNoOnly repositories whose "owner/name" contains this text (case-insensitive).
instanceYesWoodpecker instance name. Configured instances: default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Only repositories whose \"owner/name\" contains this text (case-insensitive).",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds useful non-obvious traits such as default filtering to active repos only, case-insensitive substring matching, and the fact that the entire list returns in a single response with no paging. It stops short of describing rate limits or token-scope failure behavior, so not a 5.

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?

Four sentences, tightly front-loaded with what is listed and returned, then filters, then response shape, then usage. Nearly every sentence earns its place; only the filter restatement overlaps with the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description compensates by naming the returned fields, and it covers filtering, default behavior, and the no-paging response model. An agent has everything needed to call it correctly.

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?

Schema coverage is 100%, so all three parameters are already documented in the schema. The description largely restates that ('Active repositories only unless `all` is true', name contains-match) rather than adding format or edge-case semantics, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb (Lists) and resource (repositories the instance's token can see) and even enumerates the returned fields (id, full_name, default_branch, active, forge_url), which clearly separates it from get_pipeline/list_pipelines siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly gives both the use case ('Use it to discover repositories') and the exclusion ('it isn't needed when you already know the "owner/name" slug, since the other tools accept slugs directly'), leaving nothing to inference.

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

Deploy Server

Other Tools