Postmately

Make a branded video

make_video

Queue a branded vertical video from a topic, a plan item, a template or a link to remake. Costs 60 credits; insufficient_credits says what is missing. Returns queued: poll get_video until state is ready, then pass video.id to create_post. For the person's own footage use make_video_from_my_videos instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "make_video"
  }
}

Input Schema

Name	Required	Description
`type`	No	How the video is made: explainer (narrator over cards of the brand data), wall (text over a dark clip), typography (big neon words), mascot (the logo comes alive), footage (real video on every line), promo (titles and cards to music), explainer3d (a narrated 3D animation of how something works, step by step), hook (a silent person with one line of TikTok text, then the product screens on the beat); omit to let Postmately choose
`topic`	No	What the video is about
`sourceUrl`	No	A TikTok, Reels, Shorts or VK video link to remake
`planItemId`	No	A plan item id, instead of a topic
`templateId`	No	A template slug from list_video_templates

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), it discloses the 60-credit cost, the insufficient_credits error signal, and the asynchronous nature of the call: it queues and must be polled via get_video until state is ready. That is exactly the behavior an agent cannot get 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 tight sentences: action first, then cost/error, then the queue-poll-chain workflow, then the exclusion. Every clause carries operational information and none repeats the 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 zero-required-param, async generation tool with no output schema, the description covers the full lifecycle — how it starts, that it returns a queued state, how to poll, and how to consume video.id. Nothing an agent needs to invoke and follow through is missing.

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 the enum's eight type values plus topic/sourceUrl/planItemId/templateId are already documented in the schema. The description restates the four input modes at a high level but adds no syntax, format, or precedence rules (e.g. what happens if both topic and templateId are supplied), so 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 and resource (queue a branded vertical video) and enumerates the four accepted input modes: topic, plan item, template, or remake link. It also names the sibling it is not (make_video_from_my_videos), so an agent can separate the two without opening 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 Guidelines5/5

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

Gives an explicit routing rule: use make_video_from_my_videos for the person's own footage. It also supplies the surrounding workflow conditions — what the credit cost is, what error to expect, and which tool to call next — leaving nothing to inference.

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

All Postmately 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?