gitlab-ci-mcp

Overview Schema Source Related Servers Discussions Admin

gitlab_delete_schedule

DestructiveIdempotent

Delete a GitLab CI/CD pipeline schedule by its ID; this action is permanent and cannot be undone. To pause a schedule temporarily, update it with active set to false instead.

Instructions

Delete a schedule by ID. Cannot be undone.

Examples: - "Delete schedule 42" → schedule_id=42 - If you only want to pause it temporarily, call gitlab_update_schedule with active=False instead.

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": {
      "schedule_id": "<schedule_id>",
      "project_path": "<project_path>"
    },
    "name": "gitlab_delete_schedule"
  }
}

Input Schema

Name	Required	Description	Default
`schedule_id`	Yes	Schedule ID to delete.
`project_path`	Yes	GitLab project path (e.g. 'my-org/my-repo'). Required by default. For legacy deployments only, set GITLAB_ALLOW_DEFAULT_PROJECT=true to use GITLAB_PROJECT_PATH when omitted.

Output Schema

Name	Required	Description	Default
`ref`	No
`cron`	No
`active`	No
`status`	No
`description`	No
`schedule_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.5.5Nov 5, 2026

removedInput schema / properties / project_path / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / project_path / default
```
Removed value: -null
```

changedInput schema / properties / project_path / description

Previous value: -"GitLab project path (e.g. 'my-org/my-repo'). When omitted, the default from GITLAB_PROJECT_PATH env var is used."New value: +"GitLab project path (e.g. 'my-org/my-repo'). Required by default. For legacy deployments only, set GITLAB_ALLOW_DEFAULT_PROJECT=true to use GITLAB_PROJECT_PATH when omitted."

addedInput schema / properties / project_path / minLength
```
Added value: +1
```
addedInput schema / properties / project_path / type
```
Added value: +"string"
```

changedInput schema / required

Previous value: -[
-  "schedule_id"
-]New value: +[
+  "schedule_id",
+  "project_path"
+]

First observedv0.5.1Apr 17, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. The description reinforces this with 'Cannot be undone' and, more valuably, offers the non-destructive pause path — context beyond the annotations, though it does not add permission requirements or failure behavior.

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?

The irreversible consequence is front-loaded in the first two sentences, and the examples block is short and directly actionable. No sentence is filler or restates the tool name.

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?

An output schema exists, so return values need no explanation. For a two-parameter destructive tool, the definition covers purpose, irreversibility, the correct alternative, and a usage example — nothing an agent needs to invoke it correctly is missing.

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 both schedule_id and project_path are already documented, including the legacy default-project fallback. The example 'Delete schedule 42' → schedule_id=42 adds only a trivial mapping, not new meaning, so the baseline of 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?

The description states a specific verb and resource ('Delete a schedule by ID') and immediately qualifies scope with irreversibility. An agent can distinguish it from gitlab_list_schedules, gitlab_create_schedule, and gitlab_update_schedule without opening any schema.

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 explicitly routes the agent away from this tool when the intent is temporary: 'If you only want to pause it temporarily, call gitlab_update_schedule with active=False instead.' That is a concrete when-not-to-use rule naming the exact alternative and the parameter value that selects it.

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