Postemi: Social Media Scheduler

preview_post

Read-onlyIdempotent

Preview a social media post before it is posted or scheduled: shows exactly what create_post would send to Facebook, Instagram, X (Twitter), LinkedIn, TikTok, YouTube, Threads, Bluesky, Pinterest and the other channels, WITHOUT writing anything.

Takes the same socialPost array as create_post. Per account it returns the platform, name and @handle, the publish time in the user's local timezone, the character count against that account's limit, the text as the platform receives it, and every problem that would make create_post refuse. "warnings" lists what create_post changes without refusing (on X, links are removed; the text shown is already without them) and what will probably not go out (some platforms accept only so many posts from one account in 24 hours; a post after the trial or the subscription ends).

Show the result and call create_post only after the user agrees; the @handle tells similar accounts apart. When a problem is a QUESTION (for example who may reply on X), ask it once and pass the answer in settings for later posts on that platform. Never guess a value the user did not give.

Magyarul: poszt előnézete posztolás vagy ütemezés előtt.

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": {
      "socialPost": "<socialPost>"
    },
    "name": "preview_post"
  }
}

Input Schema

Name	Required	Description	Default
`socialPost`	Yes	Individual post

Output Schema

Name	Required	Description	Default
`errors`	No
`output`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover read-only, non-destructive and idempotent, but the description adds real substance: the problems-vs-warnings distinction, that warnings include things create_post silently changes (X link removal) and rate/subscription limits, and that the @handle disambiguates similar accounts. The only gap is that it doesn't mention cost or latency of previewing many accounts at once.

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?

Front-loaded with the verb and the no-write guarantee, then organized into returns, warnings, and workflow. The channel enumeration and duplicate 'into the user's local timezone' phrasing add bulk without much decision value, and the trailing Hungarian line is noise for an agent, but nothing critical is buried.

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?

An output schema exists, so return values needn't be spelled out, yet the description summarizes the per-account result shape anyway. Combined with the warnings/problems taxonomy and the follow-up workflow, an agent has everything needed to call this and act on the output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description earns extra credit by tying socialPost to create_post's identical array and explaining the per-account return semantics (platform, handle, local publish time, character count against limit, post-transform text). It also explains a parameter behavior not in the schema: omitting settings reveals what is missing.

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 ('Preview a social media post') and immediately defines scope relative to the sibling: it shows exactly what create_post would send without writing anything. The create_post comparison makes the boundary between the two tools unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit workflow: show the result and call create_post only after the user agrees. It also covers the question case ('ask it once and pass the answer in settings') and the 'never guess a value' rule, plus a concrete technique (omit settings to see what is still missing).

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

All Postemi: Social Media Scheduler 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.