Skip to main content
Glama

Social0

schedule_post

Destructive

Schedule an existing unpublished Social0 draft for future publishing at a specific date and time. Example: 'Schedule tomorrow's announcement at 9 AM.'

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": {
      "post_id": "<post_id>",
      "scheduled_at": "<scheduled_at>"
    },
    "name": "schedule_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
mediaNoOptional media IDs from upload_media to attach before scheduling
post_idYesDraft ID to schedule
platformsNoOptional subset of platforms/account IDs
scheduled_atYesISO 8601 datetime, e.g. 2026-07-12T09:00:00.000Z
platform_optionsNoAdvanced per-platform settings. Supports content/caption and media per platform, plus pinterest board_id/title/link/create_board, tiktok title/privacy/draft/comment/duet/stitch/commercial/AI flags, instagram cover_image_url/trial_reel, youtube title, and x/twitter_x madeWithAi/paidPartnership.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already disclose destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds the useful precondition that the draft must be unpublished, but says nothing about what happens to the draft after scheduling, whether re-calling creates duplicate scheduled posts (a real risk given non-idempotency), or failure behavior.

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?

Two short sentences with the core action front-loaded and a concrete example that clarifies the datetime intent. The example is mildly redundant with the schema's ISO example but does illustrate intent, so it earns most of its space.

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

Completeness3/5

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

For a 5-parameter, non-idempotent mutation with a nested platform_options object and no output schema, the description covers the happy path but omits result information (what ID/status comes back) and duplicate-scheduling risk. The rich schema compensates for parameter gaps, so this is adequate rather than complete.

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% and every parameter, including the nested platform_options object, is documented in the schema itself. The description only echoes the datetime concept via its example ('9 AM'), adding no format, ordering, or default semantics beyond what the schema provides.

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?

States a specific verb+resource ('Schedule an existing unpublished Social0 draft') and constrains the input to drafts, which is more precise than a generic 'schedule'. However, with siblings named schedule_content and publish_now, the description never says how this differs from those, leaving sibling disambiguation to inference.

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

Usage Guidelines3/5

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

The 'existing unpublished draft' + 'future publishing' phrasing implies the precondition (draft must already exist and not be published) and the temporal constraint. There is no explicit when-not guidance, no mention of publish_now or schedule_content as alternatives for different cases.

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.