Skip to main content
Glama

Schedule Social Post

schedule_social_post
Destructive

[publish] Schedule one approved draft, or reschedule a FAILED post: sets its publish time (ISO datetime with offset, must be > 1 minute ahead) and, when given, the approved caption text. A FAILED post goes back to SCHEDULED and is retried at that time (error cleared). platform = ig|fb|tw|tt|yt|li|th|tg|bsky; post_id = _post_id, or pass post_uuid. The post goes live at that time without further confirmation.

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": {
      "platform": "<platform>"
    },
    "name": "schedule_social_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
captionNo
post_idNo
platformYes
post_uuidNo
schedule_datetimeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations it discloses the state machine (FAILED returns to SCHEDULED with the error cleared and is retried), a hard precondition (publish time must be more than one minute ahead), the datetime format requirement (ISO with offset), and an irreversibility warning that the post goes live with no further confirmation. That is exactly the operational context an agent needs for a destructive, non-idempotent, open-world mutation.

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?

It is dense but front-loaded, leading with the action and scope before the mechanics. The single run-on sentence packs state transitions, formats, and warnings together, which costs a little readability but contains no 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 mutation with five undocumented-in-schema parameters and no output schema, the definition covers preconditions, identifier formats, and side effects well. It omits only peripheral details such as permission requirements and the exact response shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description carries the full burden and largely does: it enumerates the platform codes, defines post_id as '<platform>_post_id', presents post_uuid as an alternative identifier, constrains schedule_datetime to ISO with offset and >1 minute ahead, and explains caption as the approved caption text supplied 'when given'. Only the nullability/optionality of caption and post_uuid is left to 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 gives a specific verb and resource ('Schedule one approved draft, or reschedule a FAILED post') and scopes the operation to setting a publish time plus optional caption. It implicitly separates itself from an immediate-publish sibling by stating 'The post goes live at that time,' but it never names or explicitly contrasts any sibling tool.

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?

It states the two valid entry conditions clearly: an approved draft to schedule, or a FAILED post to reschedule. It stops short of naming alternatives (e.g. publishing immediately vs. scheduling) or stating what happens if the post is in another state such as already SCHEDULED.

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.

Resources