Skip to main content
Glama

gitlab_create_schedule

Create scheduled CI/CD pipelines in GitLab using cron expressions and custom variables to automate repetitive builds and deployments.

Instructions

Create a new CI/CD schedule with the given cron and variables.

Not idempotent: duplicate calls create duplicate schedules with auto-incrementing IDs.

Examples: - "Schedule a nightly build on master at 02:00 Europe/Berlin" → description='Nightly build', cron='0 2 * * *', ref='master', timezone='Europe/Berlin', variables={'NIGHTLY': '1'} - Don't use to update existing schedules — use gitlab_update_schedule.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionYesHuman-readable description.
cronYesCron expression in 5 fields (e.g. '0 2 * * *').
variablesYesCI variables to attach to the schedule (key -> value).
refNoBranch or tag to run.master
timezoneNoIANA timezone for the cron (e.g. 'Europe/Berlin').UTC
activeNoActivate the schedule immediately.
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
Behavior4/5

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

The description adds valuable behavioral context beyond annotations: explicitly states 'Not idempotent: duplicate calls create duplicate schedules with auto-incrementing IDs' which clarifies the idempotentHint=false annotation. It also mentions the tool creates new resources (consistent with annotations) and provides practical examples of how it behaves.

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?

Extremely efficient structure: purpose statement first, critical behavioral warning next, practical examples, then explicit usage boundary. Every sentence earns its place with zero wasted words, and the Markdown formatting enhances readability without adding fluff.

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?

Complete for a creation tool: purpose is clear, usage boundaries defined, behavioral traits explained, parameters illustrated through examples. With comprehensive annotations and output schema existing, the description focuses exactly on what's needed for an agent to understand when and how to use this tool correctly.

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?

With 100% schema description coverage, the schema already documents all 7 parameters thoroughly. The description provides helpful examples showing how parameters combine (e.g., description='Nightly build', cron='0 2 * * *', etc.), adding practical context beyond the schema's technical definitions.

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 verb 'Create' and resource 'new CI/CD schedule', specifying it's for CI/CD with cron and variables. It distinguishes from sibling gitlab_update_schedule by emphasizing this is for creation only, not updates.

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?

Explicitly states when NOT to use this tool ('Don't use to update existing schedules') and names the alternative tool gitlab_update_schedule. The example provides concrete usage scenarios, and the non-idempotent warning guides against duplicate calls.

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