Skip to main content
Glama

gitlab_update_schedule

DestructiveIdempotent

Modify GitLab CI/CD pipeline schedules by updating fields like cron expressions, active status, or variables. Replace entire variable sets when specified, or adjust specific schedule parameters without affecting others.

Instructions

Update an existing schedule. Only provided fields change.

Destructive when variables is set: the entire variable set is replaced, so ensure the caller sends a full list.

Examples: - "Deactivate schedule 42" → schedule_id=42, active=False - "Change cron of schedule 42 to hourly" → schedule_id=42, cron='0 * * * *' - Don't pass variables unless you want to replace them entirely.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
schedule_idYesSchedule ID to update.
descriptionNoNew description.
cronNoNew cron expression.
refNoNew ref (branch/tag).
activeNoNew active state.
variablesNoNew variable set. If provided, **replaces all existing variables** — pre-existing ones are deleted first. Omit to leave variables untouched.
project_pathNoGitLab project path (e.g. 'my-org/my-repo'). When omitted, the default from GITLAB_PROJECT_PATH env var is used.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
schedule_idNo
statusNo
descriptionNo
cronNo
refNo
activeNo
Behavior5/5

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

While annotations already indicate destructiveHint=true, the description adds crucial behavioral context by specifying that destruction only occurs when 'variables' is set, explaining the full replacement behavior. It also clarifies the partial update nature ('Only provided fields change') and provides concrete examples of different update scenarios, adding significant value beyond the annotations.

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 description is efficiently structured with clear sections: purpose statement, critical warning about destructive behavior, and practical examples. Every sentence serves a distinct purpose without redundancy, and the information is front-loaded with the most important behavioral warning appearing early.

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?

Given the tool's complexity (mutation with destructive potential), the description provides complete context: purpose, behavioral nuances, parameter guidance, and usage examples. With annotations covering safety aspects and an output schema present, the description focuses appropriately on the practical usage information an agent needs to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the baseline is 3. The description adds meaningful context about the 'variables' parameter's destructive replacement behavior and provides practical examples showing how parameters like 'active' and 'cron' are used in real scenarios, offering semantic guidance beyond the schema's technical documentation.

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 clearly states the specific action ('Update an existing schedule') and resource ('schedule'), distinguishing it from sibling tools like gitlab_create_schedule and gitlab_delete_schedule. The opening sentence provides immediate clarity about the tool's function.

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?

The description provides explicit guidance on when to use this tool (for updating schedules) and when to be cautious (with the variables parameter). It distinguishes from alternatives by contrasting with gitlab_create_schedule and gitlab_delete_schedule, and includes practical examples showing different update scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mshegolev/gitlab-ci-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server