Skip to main content
Glama

set_trigger_schedule

DestructiveIdempotent

Change how often the trigger checks, from the choices the Studio's schedule form has: every N minutes or hours (frequency "custom", with every and unit; N must split the hour or day evenly), "daily", "weekly" (daysOfWeek 0 = Sunday to 6 = Saturday) or "monthly" (day 1 to 28). Give times as the user's own clock (hour 0-23, minute); never convert to UTC, and pass timeZone for a time of day. It takes effect at once, with no publish. It changes how often every playbook that uses the trigger gets items, and how often the app is called: when more than one playbook uses it, confirm with the user first. The answer lists when it will really run next.

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": {
      "triggerId": "<triggerId>",
      "frequency": "<frequency>"
    },
    "name": "set_trigger_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
hourNoFor daily, weekly, monthly: 0-23, on the user's clock.
unitNoFor custom.
everyNoFor custom: every N, from 1, 2, 3, 4, 5, 6, 10, 12, 15, 20, 30 minutes or 1, 2, 3, 4, 6, 8, 12 hours.
minuteNoFor daily, weekly, monthly: 0-59.
timeZoneNoThe user's IANA time zone, e.g. "Australia/Sydney". Pass it when you know it: times are read back on the user's own clock and never in UTC. Without one, a time of day is refused and no clock times are shown.
frequencyYes
triggerIdYesThe trigger's id, from list_triggers or create_trigger.
dayOfMonthNoFor monthly: 1 to 28.
daysOfWeekNoFor weekly: 0 (Sunday) to 6 (Saturday).

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true) the description explains the blast radius: the change affects how often every playbook using the trigger gets items and how often the app is called. It also discloses timing (takes effect at once, no publish) and that the response lists the actual next run times, which is exactly the extra context annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The most important facts — what changes and its immediate effect — are front-loaded, and the sentences are dense with actionable detail rather than filler. The first sentence is a long run-on with nested quoting, which costs some readability.

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?

For a 9-parameter mutation tool with no output schema, the description covers effect timing, cross-playbook impact, confirmation requirements, timezone handling, and even what the response contains. An agent has everything needed to call it correctly and safely.

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 89%, so the baseline is 3; the description adds a genuinely new constraint that 'N must split the hour or day evenly' and reinforces the user-clock/no-UTC rule, which shapes how the agent should populate values. Much of the rest (day ranges, daysOfWeek 0=Sunday, hour 0-23) duplicates the schema descriptions rather than extending them.

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?

The description opens with a specific verb and resource ('Change how often the trigger checks') and enumerates the supported schedule modes, so the agent knows exactly what is being modified. It never names a sibling such as update_trigger, so the boundary between this and general trigger editing is left to inference.

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?

It gives concrete usage conditions: it takes effect immediately with no publish, and when more than one playbook uses the trigger the agent should confirm with the user first. It does not name alternative tools (e.g. pause_trigger, resume_trigger) or state when not to use it, so guidance is strong but not fully complete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources