gitlab-mcp

Update Pipeline Schedule

gitlab_update_pipeline_schedule

Update a GitLab pipeline schedule's ref, cron, timezone, active status, or inputs. Set active=false to pause it or use destroy:true to remove an input.

Instructions

Change a pipeline schedule. Pass active=false to pause it. To remove an input, pass {name, destroy: true}. Take ownership first when the schedule belongs to another user.

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": {
      "pipeline_schedule_id": "<pipeline_schedule_id>"
    },
    "name": "gitlab_update_pipeline_schedule"
  }
}

Input Schema

Name	Required	Description	Default
`ref`	No
`cron`	No
`active`	No
`inputs`	No
`project_id`	No
`description`	No
`cron_timezone`	No
`pipeline_schedule_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.7.0Nov 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive, open-world behavior, so the bar is lower; the description still adds real operational context the annotations cannot convey: how pausing works, how inputs are deleted, and the ownership prerequisite that otherwise causes a failed call. It does not describe what happens to unspecified fields or whether changes are reversible, 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.

Conciseness5/5

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

Three short sentences, each carrying distinct operational information, with the core action front-loaded and no filler or repetition.

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

Completeness3/5

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

Annotations cover the safety profile and there is no output schema to explain, but for an 8-parameter mutation with 0% schema coverage the description only addresses a fraction of the inputs (no cron/ref/timezone guidance). It is adequate to invoke safely for the two documented cases but incomplete for a full update.

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 0% across 8 parameters, so the description must carry the full burden, yet it only explains 'active' and 'inputs.destroy'. The meaning and format of ref, cron, cron_timezone, description, project_id, and inputs.name/value are left entirely undocumented.

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?

Uses a specific verb+resource ('Change a pipeline schedule') that is clearly distinct from the create/delete/get/play siblings implied by the name. It does not explicitly name an alternative tool, but the mutating scope is unambiguous.

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

Usage Guidelines4/5

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

Gives concrete usage conditions: active=false to pause, {name, destroy: true} to remove an input, and a prerequisite (take ownership first when the schedule belongs to another user). It lacks explicit when-not-to-use guidance or a named alternative (e.g. take_ownership/play siblings), which keeps it below a 5.

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

Deploy Server