Content Drifter

Save a post to the calendar

schedule_post

Saves a post on the Content Drifter calendar for a future time. By default it is saved as a draft that waits for review in the app; pass status "scheduled" to queue it. Nothing is published by this tool.

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>",
      "content": "<content>",
      "scheduledFor": "<scheduledFor>"
    },
    "name": "schedule_post"
  }
}

Input Schema

Name	Required	Description
`status`	No	Defaults to draft. A draft waits on the calendar for you to review it. "scheduled" queues it for the time given; it still needs Final Review in the app before it can auto-publish.
`content`	Yes	The post text.
`hashtags`	No	Hashtags as one string.
`mediaUrl`	No	Public image or video URL. Instagram and Pinterest need one; TikTok and YouTube need a video.
`platform`	Yes	Target network. twitter is X.
`mediaType`	No	Optional. Leave it out and the file is read to tell.
`contentType`	No	Defaults to post.
`scheduledFor`	Yes	ISO 8601 datetime when the post should go live, for example 2026-11-02T09:00:00Z.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare a non-read-only, non-idempotent, non-destructive, open-world write; the description adds meaningful context on top: the default is a draft awaiting review, and even status "scheduled" still needs Final Review in the app before auto-publish. That is exactly the kind of post-write behavior an agent needs and the annotations cannot convey. It does not warn that repeated calls create duplicate calendar entries (non-idempotent), which is the one notable gap.

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, zero waste, with the calendar-save purpose and the draft default front-loaded ahead of the publishing caveat. Every clause earns its place.

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 an 8-parameter write with full schema coverage and annotations, the description covers the critical behavioral fact (nothing publishes here, review gates apply). With no output schema, it could say what comes back (e.g., a post/calendar entry identifier) so the agent knows how to reference the saved post afterward, but otherwise it is 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 description coverage is 100%, including a detailed enum explanation for status, so the schema already carries parameter meaning. The description's restatement of draft vs scheduled largely duplicates the schema's own wording rather than adding new constraints or format detail. Baseline 3 applies when the schema does the heavy lifting.

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 ('Saves a post on the Content Drifter calendar for a future time') and immediately rules out the adjacent operation with 'Nothing is published by this tool,' which cleanly separates it from publish_now. An agent can tell what this tool does without opening the 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?

Explains the two operating modes and when each applies: default is a draft awaiting review, pass status "scheduled" to queue it. The publish_now alternative is excluded implicitly by the 'nothing is published' clause, but the description never names it or says 'use publish_now instead when you want immediate publication,' so the routing guidance stops short of explicit.

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

All Content Drifter tools Inspect

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

Need Help?