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

woodpecker-ci-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete a cron job

delete_cron
DestructiveIdempotent

Delete a scheduled cron job from a Woodpecker CI repository. Use the returned confirmation token to complete the two-step removal.

Instructions

Removes a scheduled run. If you only want it to stop for now, update_cron with enabled=false keeps the definition. Two-step.

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>",
      "cron_id": "<cron_id>"
    },
    "name": "delete_cron"
  }
}

Input Schema

NameRequiredDescriptionDefault
cron_idYesNumeric cron job id.
repo_idYesNumeric repository id. lookup_repository turns an "owner/name" pair into one; list_repositories shows both.
confirm_tokenNoToken from a previous call of this tool.

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

A4.7/5.0
Behavior5/5

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

Annotations already mark this as destructive and not read-only, but the description adds the crucial 'Two-step' behavior, indicating a confirmation token is required and this is not a single-call operation. It further contrasts with the non-destructive update_cron path, adding context beyond the structured hints.

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?

Three short sentences convey the primary action, the key alternative, and a critical workflow detail. The main action is front-loaded, and every clause earns its place without redundancy.

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?

For a destructive, two-step cron deletion tool, the description plus annotations and fully-covered schema provide everything needed: what it does, when to use it, the alternative, and the token-based confirmation flow. The output schema covers return values, so no further description is needed.

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 the baseline is 3. The description does not explain repo_id or cron_id beyond the schema, and the 'Two-step' note is behavioral rather than parameter-specific. The confirm_token parameter is already well described in the schema as a token from a previous call, so the description adds little param-level meaning.

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?

The description opens with a specific verb and resource ('Removes a scheduled run') that exactly matches the tool title. It also distinguishes itself from update_cron by explicitly framing deletion versus temporary disabling.

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?

It gives an explicit alternative: if you only want to stop the run for now, use update_cron with enabled=false. The condition (permanent removal vs. temporary stop) is clearly stated, leaving no ambiguity about when this tool should be chosen.

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