Skip to main content
Glama

Edit, pause or resume a schedule

update_schedule

Change an autopilot schedule: cadence, times, days, timezone, approval mode, run cap, stop rule, or status (active/paused/finished). Editing re-arms the next slot; pausing stops future slots without touching posts already queued.

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": {
      "schedule_id": "<schedule_id>"
    },
    "name": "update_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
timesNo
statusNo
cadenceNo
max_runsNo
timezoneNoIANA zone, e.g. Australia/Melbourne
weekdaysNo
stop_ruleNo
schedule_idYes
approval_modeNo
paused_reasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=false), it discloses real consequences: editing re-arms the next slot, and pausing halts future slots without touching already-queued posts, which is consistent with destructiveHint=false. The notable omission is partial-update semantics — whether unspecified fields are preserved or reset — plus nothing on permissions or what a "finished" status implies.

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?

Two tight sentences, front-loaded with the editable fields and followed by the state-transition consequences. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Eleven parameters with almost no schema descriptions and no output schema make this a high-burden definition, but it covers the full editable field set and the behavior of the two most consequential transitions. Missing pieces are the interaction between cadence and weekdays, paused_reason usage, and partial-update semantics for the ten optional parameters.

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?

Schema description coverage is only 9% (timezone is the only documented parameter), so the description carries most of the burden. It does map plain-language names onto several parameters (run cap → max_runs, days → weekdays, stop rule → stop_rule), but leaves the nested stop_rule fields (below, min_posts, after_posts), weekday indexing, null max_runs meaning, and the relationship between cadence "custom" and weekdays entirely to the schema.

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?

States a specific verb and resource ("Change an autopilot schedule") and enumerates the mutable surface: cadence, times, days, timezone, approval mode, run cap, stop rule, status. That distinguishes it well from a read tool like list_schedules, though no sibling is named explicitly, which keeps it just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The title broadens scope to "Edit, pause or resume," and the description implies that setting status to paused is the pause path, but there is no explicit when-to-use guidance, no mention of how to obtain schedule_id (presumably list_schedules), and no exclusions. Usage is inferable but not stated.

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