Skip to main content
Glama

Shager

by ai.shager
OverviewDiscussionsAdmin

Schedule a post

schedule_post
Destructive

Give an existing draft (or approved post) a time. The post is validated for every account (all issues at once), checked against the key's caps and the X link allowance, and — when the workspace requires approval — must be APPROVED with unchanged content. schedule_at is ISO 8601 with an offset; the workspace timezone is used for display. Each account then publishes at its own staggered time (stagger_min/max_seconds on the post), plus its per_channel.delay_minutes when the post gives a network a later time. More than 10 accounts or a start within 60 minutes needs confirmation_token from the returned plan: without it you get needs_confirmation and details.plan (accounts by network, first and estimated last dispatch, X link-post cost, TikTok notes) to show your human. The post then goes out publicly on the person's real accounts: only schedule when your human asked to publish it. Scheduling needs the publish scope and a claimed sandbox. To move a scheduled post, call schedule_post again with the new time; cancel_post stops it.

Input Schema

NameRequiredDescriptionDefault
confirmNoDeprecated boolean; does not bypass confirmation. A confirmation_token is required when a schedule goes to more than 10 accounts, starts within 60 minutes, or includes a Pinterest account. Without it you get needs_confirmation with the dispatch plan; show it to your human, then resend with confirmation_token from the returned plan.
post_idYes
schedule_atYes
workspace_idYesWorkspace id from list_workspaces
idempotency_keyNoAny unique string you choose (REST: the Idempotency-Key header works too). Retrying with the same key and body returns the first result instead of creating a second one. Kept 24 hours.
confirmation_tokenNoToken returned by needs_confirmation or validate_post for this exact plan; expires after 15 minutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / confirm / description
      Previous value: -"Deprecated boolean; does not bypass confirmation. A confirmation_token is required when a schedule goes to more than 10 accounts or starts within 60 minutes. Without it you get needs_confirmation with the dispatch plan; show it to your human, then resend with confirmation_token from the returned plan."New value: +"Deprecated boolean; does not bypass confirmation. A confirmation_token is required when a schedule goes to more than 10 accounts, starts within 60 minutes, or includes a Pinterest account. Without it you get needs_confirmation with the dispatch plan; show it to your human, then resend with confirmation_token from the returned plan."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Well beyond annotations, it discloses that the post publishes publicly on real accounts, that validation runs across all accounts at once, approval requirements, per-account staggering and per_channel.delay_minutes, and the confirmation_token gate for >10 accounts / <60 min. This is exactly the consequence/side-effect context destructiveHint implies but cannot articulate.

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?

Front-loaded with the core action and scope, then consequences and the confirmation path. It is dense and a couple of sentences pack multiple facts, but nearly every clause carries actionable information; only minor tightening would help.

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?

With no output schema, the description still explains the needs_confirmation return and the contents of details.plan (accounts by network, first/estimated last dispatch, X link cost, TikTok notes), so the agent knows what comes back and how to proceed. Nothing essential for correct invocation is missing.

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 67%, and the description adds real meaning: schedule_at is ISO 8601 with offset and displayed in workspace timezone, and confirmation_token must come from the returned plan. The deprecated confirm flag is only explained in the schema, leaving one gap where description and schema diverge.

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?

States a specific verb and resource (give an existing draft/approved post a time) and clearly separates it from create_post, update_post, and cancel_post by describing the exact operation. The final sentence maps the move vs. cancel distinction explicitly, so the agent can pick the right sibling without opening schemas.

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?

Explicit when-to-use ('only schedule when your human asked to publish it'), when-not (drafts that aren't human-approved), and alternatives ('To move a scheduled post, call schedule_post again...; cancel_post stops it'). It also states prerequisites (publish scope, claimed sandbox) needed before calling.

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

All Shager 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