Skip to main content
Glama
rolliinc

Rolli MCP

by rolliinc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_agent_schedule

Automate recurring social media monitoring reports with cron-like schedules and notify your team via email or Slack.

Instructions

Create a recurring Rolli Agent report that runs on a cron-like cadence (daily, weekly, monthly, or one-time) with optional email and Slack notifications.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoInvestigation mode (default: trend_briefing)
nameYesUser-friendly name
ends_atNoISO 8601 timestamp when the schedule stops
max_postNoPosts per platform per run (default: 100)
questionYesThe recurring question for the agent
platformsNoPlatforms to search
starts_atYesISO 8601 timestamp when the schedule becomes active
time_windowNoTime window per run (default: 7d)
notify_emailNoEmail address for run notifications
slack_team_idNoSlack workspace ID
recurrence_timeYesTime of day in HH:MM format (e.g., "09:00")
recurrence_typeYesSchedule cadence
slack_bot_tokenNoSlack bot token
slack_team_nameNoSlack workspace name
available_creditsNoReasoning effort for each run: 1=low, 2=medium, 3=high, 4=max (default)
recurrence_timezoneYesIANA timezone (e.g., "America/New_York")
notify_slack_webhookNoSlack webhook URL
recurrence_day_of_weekNo0–6 for weekly schedules (0 = Sunday)
notify_slack_channel_idNoSlack channel ID
recurrence_day_of_monthNo1–31 for monthly schedules

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.1
    • changedInput schema / properties / available_credits / description
      Previous value: -"Reasoning effort for each run: 1=low, 2=medium (default), 3=high, 4=max"New value: +"Reasoning effort for each run: 1=low, 2=medium, 3=high, 4=max (default)"
    • changedInput schema / properties / max_post / description
      Previous value: -"Posts per platform per run (default: 50)"New value: +"Posts per platform per run (default: 100)"
  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

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions 'recurring' and 'optional email and Slack notifications' but does not disclose side effects (e.g., does it immediately create an active schedule? does it require valid timezone? any validation constraints?), authorization needs, or what happens on creation. For a tool that creates a scheduled job, this is a significant gap.

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 a single, well-structured sentence. The primary action ('Create a recurring Rolli Agent report') is front-loaded, followed by cadence and notification options. No redundant wording or filler; every clause earns its place.

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

Completeness2/5

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

For a tool with 20 parameters and 6 required ones, the description is too sparse. It does not mention required fields (name, question, recurrence_type, recurrence_time, recurrence_timezone, starts_at) or any constraints (e.g., timezone format, day-of-week ranges). It also omits expected return value (there is no output schema) and any side effects like schedule activation. An agent cannot fully understand how to invoke it correctly without opening the schema.

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 coverage is 100%, so the baseline is 3. The description adds minimal semantic value: it mentions 'cron-like cadence' which hints at recurrence_type, and 'optional email and Slack notifications' which map to notify_* parameters, but these are already described in the schema. No additional meaning or examples are provided 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 clearly states the verb 'Create' and the resource 'recurring Rolli Agent report', and specifies cadence ('cron-like cadence' with daily/weekly/monthly/one-time) and optional notifications. It differentiates from update/delete/get by focusing on creation, but doesn't explicitly contrast with start_agent_run for one-time runs. The mention of 'recurring' strongly implies the distinction.

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?

No guidance is given about when to use this tool versus alternatives such as start_agent_run (for one-time execution) or update_agent_schedule (for modifying an existing schedule). The description only states what it does, not the conditions under which an agent should choose it. The context that recurring schedules are needed is implicit but not explicit.

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