Skip to main content
Glama

Schedule a text post

schedule_text
Destructive

Schedules an existing text (up to 500 characters) at publish_at, or at the next best slot with auto_optimize_time:true (the two are mutually exclusive). publish_at takes any offset and comes back in UTC (Z); a publish_at more than 60 seconds in the past returns 400 publish_at_in_past with server_now. The same account needs at least 10 minutes between scheduled posts: a closer publish_at returns 400 schedule_too_dense with nearest_publish_at. Checked against the account's content_rules: with enforce:block a violation returns 422 and nothing is scheduled; the post is checked again right before it publishes. Applies for text-only posts with a specific time or when the user wants the system to pick the time.

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": {
      "account_id": "<account_id>",
      "text": "<text>"
    },
    "name": "schedule_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText
account_idYesAccount id
publish_atNoISO 8601 with offset (canonical time field)
schedule_atNoDeprecated alias of publish_at
auto_optimize_timeNoNext best slot (mutually exclusive with publish_at)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare the write/destructive profile; the description goes well beyond them with UTC normalization on return, a 60-second past-tolerance returning 400 publish_at_in_past with server_now, a 10-minute density floor returning 400 schedule_too_dense with nearest_publish_at, and content_rules enforcement semantics including a pre-publish re-check. These are exactly the failure modes an agent needs before attempting a call.

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?

Every sentence carries operational content — limits, error codes, spacing rules, enforcement — with the happy path front-loaded before constraints. It reads as one dense block rather than being segmented, but no sentence is filler.

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?

For a destructive, non-idempotent write with no output schema, the description covers the major behavioral risks (timing constraints, content rules, pre-publish re-validation). It does not address idempotency or how to undo/amend a scheduled post, which leaves a small gap.

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 100%, so the baseline is 3, but the description adds meaning the schema does not: publish_at accepts any offset and comes back as UTC (Z), the past-window constraint, and how auto_optimize_time interacts with publish_at. The deprecated schedule_at alias is only covered by the schema, not the description.

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 verb and resource ('Schedules an existing text') and immediately pins scope: up to 500 characters, at publish_at or the next best slot, and text-only posts. An agent can distinguish this from library-generation siblings without opening any schema.

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

Usage Guidelines4/5

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

The closing sentence gives explicit when-to-use conditions: text-only posts with a specific time, or when the user wants the system to pick the time. The mutual exclusivity of publish_at and auto_optimize_time is stated as an operating rule. No alternative tool is named (e.g., cancel_schedule for undo), so it stops short of a 5.

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.