Skip to main content
Glama
Content Drifter MCP

Content Drifter MCP

Official
by OPTRIXTECH

schedule_post

Schedule a social post for a future ISO 8601 datetime on the Content Drifter calendar; complete Final Review in the dashboard before auto-publish.

Instructions

Schedule a post on the Content Drifter calendar for a future ISO datetime. User must complete Final Review in the dashboard before auto-publish.

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

NameRequiredDescriptionDefault
contentYes
hashtagsNo
imageUrlNoPublic image URL. Required by Instagram, Pinterest and TikTok.
platformYesTarget network. twitter is X.
contentTypeNoDefaults to post
scheduledForYesISO 8601 datetime when the post should go live

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the post does not go live immediately and that a dashboard Final Review gate precedes auto-publish, but it omits whether scheduling errors out when review is incomplete, what state the post is created in, and what is returned.

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 primary action and its timing constraint front-loaded; nothing is padded. The phrase 'before auto-publish' is slightly compressed and leaves the consequence of an incomplete review unstated.

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 six-parameter mutation with no annotations and no output schema, the description covers the scheduling intent and the review gate but says nothing about failure modes, platform-specific validation, or the resulting post state. It is adequate but leaves real gaps for an agent to discover by trial.

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 moderate at 67%, and the description adds essentially no parameter meaning beyond restating that scheduledFor is an ISO datetime, which the schema already documents. Platform enum values, the contentType default, and the Instagram/Pinterest/TikTok imageUrl requirement are all handled by the schema, not the description.

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 names a specific verb-plus-resource ('Schedule a post on the Content Drifter calendar') and scopes it with 'for a future ISO datetime,' which implicitly separates it from an immediate-publish sibling like publish_now. It stops short of naming any sibling, so differentiation must be inferred from the verb rather than stated.

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 future-datetime constraint signals the appropriate context, and the Final Review note reads as a precondition. However, it never explicitly contrasts with publish_now or list_upcoming_posts, and it's unclear whether an incomplete Final Review causes the call to fail or merely blocks auto-publish.

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