Skip to main content
Glama

gitlab_create_schedule

Create a new GitLab CI/CD schedule with a cron expression, branch, timezone, and variables. Each call generates a distinct schedule.

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
Behavior5/5

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

Discloses non-idempotent behavior ('duplicate calls create duplicate schedules with auto-incrementing IDs'), which goes beyond annotations. No contradiction with annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false).

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?

Concise: one-line purpose, a behavioral note, and two well-structured examples. Front-loaded with key information, every sentence adds value.

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 7 parameters and nested objects, the description covers purpose, non-idempotency, usage alternative, and a practical example. Output schema exists, so return values need not be described.

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?

Input schema has 100% coverage with clear descriptions. The description adds an illustrative example showing parameter usage together, enhancing practical understanding beyond schema alone.

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 'Create a new CI/CD schedule' with specific verb and resource, and differentiates from sibling tools by explicitly noting not to use for updates, referencing gitlab_update_schedule.

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 warns 'Don't use to update existing schedules — use gitlab_update_schedule instead', and notes non-idempotency, providing clear guidance on when to use and when not.

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