Skip to main content
Glama
Sign In
Rolli MCP

Rolli MCP

by rolliinc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_agent_schedule

Partially update a Rolli Agent schedule without overwriting unspecified fields, and recalculate next_run_at automatically when recurrence settings change.

Instructions

Partially update a Rolli Agent schedule. Unspecified fields are left unchanged. next_run_at is recalculated if any recurrence parameter changes.

Input Schema

NameRequiredDescriptionDefault
idYesSchedule UUID
modeNoNew investigation mode
nameNoNew schedule name
ends_atNoNew end ISO 8601 timestamp
max_postNoNew posts-per-platform limit
questionNoNew question
platformsNoNew platforms array
starts_atNoNew start ISO 8601 timestamp
time_windowNoNew time window
notify_emailNoNew notification email
recurrence_timeNoNew time of day in HH:MM format
recurrence_typeNoNew cadence
available_creditsNoNew reasoning effort: 1=low, 2=medium, 3=high, 4=max
recurrence_timezoneNoNew IANA timezone
notify_slack_webhookNoNew Slack webhook URL
recurrence_day_of_weekNo0–6 for weekly schedules
notify_slack_channel_idNoNew Slack channel ID
recurrence_day_of_monthNo1–31 for monthly schedules

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • addedInput schema / properties / max_post / maximum
      Added value: +9007199254740991
  2. Changed1 schema field changedv1.4.0
    • changedInput schema / properties / platforms / items / enum
      Previous value: -[
-  "twitter",
-  "reddit",
-  "bluesky",
-  "youtube",
-  "threads",
-  "facebook",
-  "weibo"
-]New value: +[
+  "twitter",
+  "reddit",
+  "bluesky",
+  "youtube",
+  "threads",
+  "facebook"
+]
  3. Addedv1.3.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that unspecified fields are left unchanged and that next_run_at is recalculated when recurrence parameters change, but it omits permissions, validation behavior, error handling, and whether updates affect currently running schedules.

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 three short sentences, front-loaded with the core action and partial-update semantics. Every sentence adds relevant information about behavior without unnecessary wording.

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

Completeness3/5

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

For an 18-parameter mutation tool with no annotations and no output schema, the description covers the most important update semantics: partial updates and next_run_at recalculation. However, it leaves out prerequisite state, permission requirements, and side effects that would help an agent invoke it confidently.

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 100%, so the schema already documents all 18 parameters in detail, including enum values and ranges. The description adds useful context about recurrence parameters triggering next_run_at recalculation, but otherwise does not add meaning beyond 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?

The description states a specific verb and resource: 'Partially update a Rolli Agent schedule.' The word 'Partially' distinguishes it from a full replacement update, and the resource is unambiguous, though it does not explicitly name sibling tools like pause_agent_schedule or create_agent_schedule.

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

Usage Guidelines2/5

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

The description does not say when to use this tool versus alternatives such as pause_agent_schedule, resume_agent_schedule, or create_agent_schedule. Usage is only implied by the 'partially update' wording, with no explicit context or exclusions.

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

Deploy Server

Other Tools