Content Drifter

Write a post

generate_post

Writes one platform-native social post and a suggested image prompt from a topic, using the account Brand Kit voice. Returns the text and its hashtags and does not save or publish anything.

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

Name	Required	Description
`tone`	No	Optional tone override.
`topic`	Yes	What the post is about.
`length`	No	Optional length hint.
`brandId`	No	Optional workspace id for accounts that manage more than one client brand. list_workspaces returns the ids. Omit it for the primary workspace.
`platform`	Yes	Target network. twitter is X.

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 readOnlyHint=false and non-idempotent, which could imply a persisting write; the description usefully resolves that by stating nothing is saved or published and that the output is returned as text plus hashtags. It also discloses the Brand Kit voice dependency, though it says nothing about cost, latency, or failure modes for unsupported platforms.

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 dense sentences with the core capability first and the non-persistence guarantee second. No filler, and the most decision-relevant constraint lands before the agent stops reading.

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 a 5-parameter, no-output-schema tool, the description covers inputs, the no-side-effect guarantee, and the return payload. Minor gap: it names the image prompt as generated but omits it from the 'Returns the text and its hashtags' sentence, leaving the full return shape slightly ambiguous.

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%, so the schema already explains platform, topic, tone, length, and brandId. The description reinforces 'topic' and the platform-native targeting but adds no new semantics for tone, length, or brandId beyond what the enum and property descriptions already provide.

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 (writes) and a precise deliverable (one platform-native social post plus a suggested image prompt) derived from a topic and Brand Kit voice. The closing clause 'does not save or publish anything' separates it from publish_now and schedule_post without needing to open either 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?

The 'does not save or publish anything' clause gives a clear when-not and implicitly routes drafting to this tool and persistence to the publish/schedule siblings. It stops short of naming those alternatives or stating prerequisites (e.g. fetching the Brand Kit first), so the routing is inferential rather than 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?