QPost

by io.github.arslan2012

create_post

Create and publish (or schedule) a video or image post to connected platforms. Media must be supplied as a publicly reachable URL (mediaUrl / imageUrls) or base64 (mediaBase64) — this is a hosted server and cannot read files from your machine. Omit scheduledFor to publish immediately.

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": {
      "caption": "<caption>",
      "platforms": "<platforms>",
      "mediaKind": "<mediaKind>"
    },
    "name": "create_post"
  }
}

Input Schema

Name	Required	Description
`title`	No	Optional title (YouTube)
`caption`	Yes	Main text/caption of the post
`mediaUrl`	No	Publicly reachable URL of the video or single image
`timezone`	No	IANA timezone, default "UTC"
`imageUrls`	No	Multiple image URLs for a carousel
`mediaKind`	Yes
`platforms`	Yes
`mediaBase64`	No	Base64-encoded media bytes, if you have no public URL
`scheduledFor`	No	ISO datetime; omit to publish immediately
`mediaFilename`	No	Filename for mediaBase64, e.g. clip.mp4 — sets the MIME type

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations only declare openWorldHint and destructiveHint=false, so the description carries most of the behavioral burden and does well: it discloses that the server is hosted and cannot access local files, and that omission of scheduledFor publishes immediately rather than saving a draft. It doesn't cover multi-platform partial failure behavior or what the call returns, which matters for a fan-out publish.

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 sentences, front-loaded with the action, then the two constraints an agent most often gets wrong (media ingestion, scheduling). No filler or restated field names.

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?

No output schema exists, yet the description never says what a successful call returns (post id? per-platform results?) or how partial failures across multiple platforms are reported — significant for a 10-parameter fan-out publish. Media-source and scheduling rules are covered, so it is adequate but incomplete.

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?

With 80% schema coverage the baseline is 3, and the description earns above that by explaining the alternative media-input paths (public URL vs base64) and the publish-now semantics of scheduledFor. It doesn't clarify that mediaFilename sets the MIME type for base64 input or how platform metadata is structured, but the schema covers those.

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 ('Create and publish (or schedule) a video or image post to connected platforms'), and the scheduling/publishing duality immediately separates it from update_post and retry_post. An agent can identify the operation without opening the 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?

'Omit scheduledFor to publish immediately' gives an explicit conditional rule for the two modes of use. It also rules out local file paths ('cannot read files from your machine'), which is a real invocation error mode. It stops short of naming alternatives (update_post for existing posts, retry_post for failures).

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

All QPost 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.