Skip to main content
Glama

Social0

schedule_content

Destructive

Create content and schedule it for future publishing in one step (does not publish immediately). Example: 'Schedule a LinkedIn post about our launch for tomorrow 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": {
      "content": "<content>",
      "platforms": "<platforms>",
      "scheduled_at": "<scheduled_at>"
    },
    "name": "schedule_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
mediaNoMedia IDs from upload_media
contentYesPost caption
platformsYesTarget platforms or account IDs
scheduled_atYesISO 8601 datetime to publish
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

A3.5/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the description's main added value is the deferred-effect clarification that nothing is published at call time. It does not explain what makes the operation destructive, that repeated calls create duplicate scheduled entries, or what account/permission prerequisites apply.

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?

Two sentences: the core behavior with its key negative constraint is front-loaded, followed by one concrete example. No redundant or filler text.

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 mutating, non-idempotent tool with a nested options object and no output schema, the description states purpose and timing semantics but omits what a successful call returns (scheduled post ID/status), how partial platform failures are handled, and any duplicate-prevention guidance. Adequate to invoke, thin for calling correctly under error conditions.

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 is documented in-schema, so the baseline applies. The example loosely illustrates platforms and scheduled_at usage but adds no format or constraint detail beyond the schema (e.g., required vs optional platform_options behavior).

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?

"Create content and schedule it for future publishing in one step" states a specific verb (create+schedule) and resource (content/post), and the parenthetical "does not publish immediately" separates it from immediate-publish siblings like publish_now. It does not, however, distinguish itself from the very similar sibling schedule_post, leaving an ambiguity an agent must resolve elsewhere.

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 example ("Schedule a LinkedIn post about our launch for tomorrow at 9 AM") conveys a realistic usage scenario, and the "does not publish immediately" clause implies when this is preferred over publishing right away. There are no explicit exclusions and no named alternative (schedule_post, create_draft, publish_now) to route between.

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.