Revid

Publish now

publish_now

Destructive

Publish a rendered video immediately using the selected channel or connected accounts (TikTok, YouTube, Instagram, X, Facebook Pages, webhook). Use list_social_accounts first to find ids and handles.

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": {
      "videoUrl": "<videoUrl>"
    },
    "name": "publish_now"
  }
}

Input Schema

Name	Required	Description
`x`	No	Post the video to a connected X (Twitter) account. Pick the destination from `list_social_accounts` (platform "x"): pass its id, or its username. Video must be 2:20 or shorter (10 min on X Premium), max 512 MB. Skip accounts with tokenInvalid: true and ask the user to reconnect them in Revid settings.
`tiktok`	No	Post to a connected TikTok account: { id or username, title?, privacy_level? }.
`webhook`	No	Send the video to a configured webhook: { id or username, title?, description? }.
`youtube`	No	Post to a connected YouTube channel: { id or username, title?, description? }.
`facebook`	No	Post the video to a connected Facebook Page (Pages only, not personal profiles). Pick the destination from `list_social_accounts` (platform "facebook"): pass its id, or its name. Skip Pages with tokenInvalid: true and ask the user to reconnect them in Revid settings.
`videoUrl`	Yes	Public URL for the video to publish.
`channelId`	No	Saved Revid channel id (channels[].id from `list_social_accounts`). A channel bundles several accounts; mutually exclusive with per-platform accounts.
`instagram`	No	Post to a connected Instagram account: { id or username, caption? }.
`channelName`	No	Saved Revid channel name (channels[].name from `list_social_accounts`).
`extraParams`	No	Additional content metadata forwarded to Revid. extraParams.title and extraParams.description are the default caption/title/description for every destination; extraParams.thumbnailUrl the default cover. A default title longer than a destination's title limit (YouTube 100, webhook 100, Facebook 255 characters) is shortened for that destination, at a word boundary when possible; captions keep it whole. An explicit youtube.title, webhook.title or facebook.title over its limit is refused, never shortened.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`error`	No
`method`	Yes
`status`	Yes
`endpoint`	Yes
`retryAfterSeconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the risk profile is partly covered. The description adds that publication is immediate and to external platforms, but never says the post goes live publicly and cannot be recalled, nor anything about failure/partial-failure across multiple destinations. The richer behavioral detail (tokenInvalid handling, per-platform size limits) lives in the schema, not the description.

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 tight sentences, with the action and destination scope front-loaded and the prerequisite second. Nothing redundant and nothing padded.

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?

For a destructive, open-world, 10-parameter publishing tool, the description is thin: it does not state whether multiple destinations can be published in one call, what happens if one destination fails, or that credits are consumed. The output schema covers return values and the schema covers parameters, but the operational semantics an agent needs before firing an irreversible post are left implicit.

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 the schema already documents every parameter, including the channelId vs per-platform mutual exclusivity and the extraParams title-shortening rules. The description only gestures at "the selected channel or connected accounts", which adds no syntax or precedence detail beyond the schema. 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?

"Publish a rendered video immediately" gives a specific verb, resource and timing, and the enumeration of supported destinations (TikTok, YouTube, Instagram, X, Facebook Pages, webhook) frames the scope precisely. The word "immediately" implicitly separates it from schedule_publish among the siblings, so an agent can pick it 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?

It gives an explicit prerequisite workflow: "Use `list_social_accounts` first to find ids and handles." That is real, actionable routing guidance. It falls short of 5 because it never names schedule_publish as the alternative for future-dated posts, nor states when not to use it (e.g. before a render completes).

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

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