Skip to main content
Glama
Content Drifter MCP

Content Drifter MCP

Official
by OPTRIXTECH

generate_post

Drafts a platform-native social post from your Brand Kit, with a matching image prompt, when you need content tailored to a specific network, topic, and tone.

Instructions

Generate a platform-native social post and suggested image prompt using the user Brand Kit. Use when the user asks to write or draft a post for a specific platform.

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>",
      "topic": "<topic>"
    },
    "name": "generate_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNoOptional tone override
topicYesTopic or prompt for the post
lengthNoOptional length hint
platformYesTarget network. twitter is X.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does disclose useful behavior: output includes both post copy and an image prompt, and content is derived from the user's Brand Kit. However, it never says whether anything is persisted, whether the draft must be passed to another tool to be scheduled or published, or whether listing the post afterward is needed.

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 tight sentences: the first states what is produced and from what source, the second states the trigger. Nothing is redundant and the most important information leads.

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 4-parameter generation tool with full schema coverage, the definition covers intent, inputs, and outputs adequately. It is thin on lifecycle: nothing explains that the result is ephemeral copy intended to be handed to schedule_post or publish_now, which is the main ambiguity an agent would face.

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% and two parameters carry enums, so the schema already documents platform, topic, tone, and length. The description adds only the framing that the Brand Kit drives output, with no extra meaning about how tone, length, or platform influence the result. Baseline 3 applies.

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?

"Generate a platform-native social post and suggested image prompt" names a specific verb (generate) and concrete deliverables, and "using the user Brand Kit" identifies the personalization source. It implicitly distinguishes drafting from publishing/scheduling siblings like publish_now and schedule_post, but never states that distinction explicitly.

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?

"Use when the user asks to write or draft a post for a specific platform" gives a clear triggering condition tied to intent and platform specificity. It stops short of exclusions (e.g. 'does not publish or schedule — use publish_now/schedule_post for that'), so an agent must infer where generation ends and distribution begins.

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