Skip to main content
Glama

gitlab_update_schedule

DestructiveIdempotent

Update a GitLab CI schedule's fields (cron, ref, active, description). Pass schedule_id and the fields to change; omit variables to keep them intact, or provide new set to replace all.

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?

Annotations indicate destructiveHint=true. The description adds crucial context: 'Only provided fields change' and 'Destructive when variables is set: the entire variable set is replaced.' This goes beyond annotations and provides clarity on partial updates and variable replacement 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 description is concise with 5 sentences, including examples. It opens with the core purpose, follows with behavioral details, and ends with illustrative examples. No wasted words.

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 (7 parameters, destructive behavior), the description covers essential aspects: partial update, variable replacement danger, and example usage. Output schema exists, so return values are not needed in description.

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?

Schema coverage is 100%, so baseline is 3. The description adds significant value beyond schema: it explains the destructive behavior of variables (schema mentions replacement but description emphasizes full replacement and advises caution) and provides examples showing intended usage of schedule_id, active, and cron. Not all parameters are elaborated, but the key ones are covered.

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 'Update an existing schedule' and specifies partial update behavior. It distinguishes from sibling tools like create_schedule and delete_schedule, as the name and context imply.

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 when/when-not guidance, including a strong warning about variables being destructive. Examples illustrate common use cases (deactivate, change cron) and explicitly advise against passing variables unless replacement is intended.

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