SpeedContent Social

Generate a social media post

generate_social_post

Write a social media post for a given platform and topic. The post is written to that platform's conventions, rewritten to read as human-authored, optionally scored against AI detection, and optionally illustrated with a generated image. Returns a job id immediately — poll it with check_social_job, which usually completes in 20-90 seconds. Costs credits.

Input Schema

TableJSON Schema

Name	Required	Description
`tone`	No	Defaults to friendly.
`emoji`	No	Add emoji to the post. Omit for automatic: off on LinkedIn and YouTube, on elsewhere. Set false for a clean post on any platform.
`topic`	Yes	What the post should be about.
`language`	No	Output language by name. Defaults to English.
`platform`	Yes	Target platform. Each has its own style guide and default length.
`preserve`	No	Exact lines that must appear verbatim in the finished post — a closing question, a call to action, a tagline. The humanizer rewrites sentences, so anything whose exact wording matters belongs here rather than only in the topic.
`quantity`	No	How many distinct variations to generate. Defaults to 1.
`detect_ai`	No	Score the post against AI detection and retry if it reads as machine-written. Adds 8 credits per post. Omit for automatic: runs only at 150+ words, because short posts score unreliably.
`brand_name`	No	Brand to mention where it reads naturally.
`brand_tone`	No	Voice guidance, e.g. 'Direct, no jargon'.
`word_count`	No	Target length per post. Omit to use the platform default (LinkedIn 100, YouTube 150, Facebook/Pinterest 75, Instagram/TikTok 50, X 40).
`brand_audience`	No	Who the post should speak to.
`brand_keywords`	No	Comma-separated terms to work in.
`generate_image`	No	Generate a matching image for the post. Defaults to false over MCP; pass true to request one. Adds 10 credits per post.
`brand_description`	No	What the business does.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 3, 2026

addedInput schema / properties / emoji

Added value: +{
+  "description": "Add emoji to the post. Omit for automatic: off on LinkedIn and YouTube, on elsewhere. Set false for a clean post on any platform.",
+  "type": "boolean"
+}

changedInput schema / properties / generate_image / description

Previous value: -"Generate a matching image. Defaults to true. Adds 10 credits per post."New value: +"Generate a matching image for the post. Defaults to false over MCP; pass true to request one. Adds 10 credits per post."

addedInput schema / properties / preserve

Added value: +{
+  "description": "Exact lines that must appear verbatim in the finished post — a closing question, a call to action, a tagline. The humanizer rewrites sentences, so anything whose exact wording matters belongs here rather than only in the topic.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

First observedOct 2, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnly=false, openWorld=true, idempotent=false) by disclosing that the call is asynchronous, returns a job id rather than content, takes 20-90 seconds, and consumes credits. These are the details an agent most needs and none are derivable from the structured fields.

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?

Three dense sentences, front-loaded with the core purpose and terminating with the two facts an agent must act on (async job id + polling, credit cost). No redundant restatement of name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 15-parameter async generation tool with no output schema, the description supplies the missing pieces: the return contract (job id), the follow-up tool, expected latency, and cost signaling. Combined with a fully documented schema, an agent has everything needed to invoke and follow through.

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%, so every parameter (tone, emoji, detect_ai, generate_image, word_count, preserve, etc.) is already documented in the schema, including defaults and credit costs. The description only gestures at the optional AI-scoring and image features, adding no syntax or format detail beyond the schema, so the baseline 3 applies.

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+resource ('Write a social media post') scoped by platform and topic, then enumerates the pipeline steps (platform conventions, humanizer rewrite, optional AI scoring, optional image). It also names the sibling it hands off to (check_social_job), so an agent can place it in the workflow without inspecting other tools.

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?

Gives clear operational context: it returns a job id immediately and must be polled via check_social_job, with a 20-90 second expectation. It does not state exclusions or when to prefer a sibling over this tool, but for a generation entry point the routing guidance is essentially complete.

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

All SpeedContent Social 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.

Generate a social media post

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources