Skip to main content
Glama

Siren

by ai.mysiren
OverviewDiscussionsAdmin

schedule_post

Destructive

Schedule a finished run to post at scheduled_at (ISO-8601). Shows in the customer's local timezone. platforms: x, instagram, tiktok, linkedin, youtube, or everything. Posts fire sequentially. Requires Allow posting. Prefer this over post_run when the user names a time. On create_campaign you can pass scheduled_at instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_idYesThe run id returned by create_campaign, render_asset, or list_runs.
captionsNoOptional caption override per platform, e.g. {"x": "...", "linkedin": "..."}.
timezoneNoIANA timezone name for scheduled_at, e.g. Africa/Lagos or America/New_York.UTC
platformsNoWhere to post: any of x, instagram, tiktok, linkedin, youtube, or ["everything"] for every connected channel.
scheduled_atYesISO-8601 time to post, e.g. 2026-09-12T09:00:00. Interpreted in the given timezone.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / captions / description
      Added value: +"Optional caption override per platform, e.g. {\"x\": \"...\", \"linkedin\": \"...\"}."
    • addedInput schema / properties / platforms / description
      Added value: +"Where to post: any of x, instagram, tiktok, linkedin, youtube, or [\"everything\"] for every connected channel."
    • addedInput schema / properties / run_id / description
      Added value: +"The run id returned by create_campaign, render_asset, or list_runs."
    • addedInput schema / properties / scheduled_at / description
      Added value: +"ISO-8601 time to post, e.g. 2026-09-12T09:00:00. Interpreted in the given timezone."
    • addedInput schema / properties / timezone / description
      Added value: +"IANA timezone name for scheduled_at, e.g. Africa/Lagos or America/New_York."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description adds meaningful behavioral context beyond the annotations: posts 'fire sequentially,' the time is 'shown in the customer's local timezone,' and it names an authorization requirement ('Requires Allow posting'). It does not contradict the annotations, and the destructiveHint is not undermined by the text.

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 compact and front-loaded with the core purpose, then provides practical usage and behavioral details in a few short sentences. Every sentence earns its place.

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 5-parameter tool with an output schema, annotations, and sibling separation, the description covers purpose, prerequisites, behavior, and alternatives. Nothing critical is missing for an agent to select and invoke this tool correctly.

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 a little extra context such as 'finished run' and platform values, but it mostly restates information already in the schema (platforms, scheduled_at, timezone).

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 opens with a specific action and resource: 'Schedule a finished run to post at scheduled_at (ISO-8601).' It clearly distinguishes the tool from its sibling post_run by stating 'Prefer this over post_run when the user names a time,' so an agent can tell them apart.

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?

The description explicitly says when to use this tool over post_run ('when the user names a time'), and points to create_campaign as an alternative ('On create_campaign you can pass scheduled_at instead'). It also states a prerequisite ('Requires Allow posting').

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

All Siren toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources