Skip to main content
Glama
Sign In
woodpecker-ci-mcp

woodpecker-ci-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create a cron job

create_cron

Schedule recurring pipeline runs in Woodpecker CI using cron expressions, descriptors, or intervals. Specify repository, job name, and schedule to trigger builds automatically.

Instructions

Schedules a pipeline run. The pipeline runs with event "cron", so steps and secrets restricted to other events do not apply to it — a cron job whose steps all have "when: event: push" runs and does nothing.

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": {
      "repo_id": "<repo_id>",
      "name": "<name>",
      "schedule": "<schedule>"
    },
    "name": "create_cron"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the cron job, shown in the UI and on the pipelines it starts.
branchNoBranch to run. Defaults to the repository default branch.
repo_idYesNumeric repository id. lookup_repository turns an "owner/name" pair into one; list_repositories shows both.
scheduleYesSchedule as a five-field cron expression ("0 4 * * *" is 04:00 daily), a descriptor (@yearly, @annually, @monthly, @weekly, @daily, @midnight, @hourly), or "@every <duration>" such as "@every 30m". No seconds field.
timezoneNoIANA time zone the schedule is interpreted in. Defaults to UTC. Note that the official Woodpecker container image carries no time zone database, so on a stock Docker deployment anything but "UTC" is rejected with "unknown time zone" — that is the server missing tzdata, not a wrong name.

Output Schema

NameRequiredDescriptionDefault
truncatedNoPresent only when the answer was shortened to fit the budget.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

With all annotation hints false, the description carries the transparency burden. It adds a genuinely non-obvious behavior: cron pipelines run with event 'cron' so event-restricted steps/secrets don't apply, illustrated by a push-only cron job doing nothing. It stops short of naming permissions or duplicate-name behavior, but the disclosed event semantics are substantial.

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

Conciseness5/5

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

Two sentences, first is front-loaded with purpose and second packs a valuable caveat with a concrete example. No filler or repetition of schema content.

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

Completeness4/5

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

With a full output schema and 100% parameter coverage, the description only needs to supply behavioral context, and it does. The main omissions are usage routing to sibling cron tools and permission requirements, which are not covered elsewhere.

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 description coverage is 100%, so the baseline is 3 even though the description adds no parameter syntax or format details. The cron-event note gives context for how schedule interacts with pipeline events, but the schema already documents each parameter thoroughly.

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 opening 'Schedules a pipeline run' gives a concrete verb and resource, and the 'event "cron"' clarification distinguishes it from manual pipeline triggers. It relies on the title/name to make clear this creates a persistent cron job rather than triggering one immediately, so it stops short of full sibling differentiation.

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

Usage Guidelines3/5

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

The description implies the use case: recurring scheduled pipeline runs via cron event. However, it never states when to prefer create_cron over update_cron, run_cron, delete_cron, or trigger_pipeline, and gives no explicit exclusions or alternatives.

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