MightyAutomation

Publish video to YouTube

grok_publish_youtube

Destructive

Upload a finished render to the workspace's connected YouTube channel (Data API v3). This is a REAL outbound publish — visibility defaults to private; use unlisted or public deliberately. Requires the channel to be connected in admin → Grok Boost first.

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": {
      "title": "<title>"
    },
    "name": "grok_publish_youtube"
  }
}

Input Schema

Name	Required	Description
`tags`	No	Up to 30 tags.
`title`	Yes	Video title (max 100 chars).
`render_id`	No	video_renders id (uuid) from grok_generate_video — or pass video_path.
`video_path`	No	video-renders storage path under this owner, alternative to render_id.
`visibility`	No	Default private.
`description`	No	YouTube description text.

Output Schema

Name	Required	Description
`ok`	No
`url`	No
`error`	No	Present only when ok is false.
`video_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare the mutation profile (destructive, openWorld, non-idempotent), so the bar is lower, but the description still adds real context: this is a REAL outbound publish, the default visibility, and an admin-side connection requirement. Quota/rate-limit behavior for the YouTube Data API is the only notable omission.

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, front-loaded with the action and the most consequential fact (a real publish), with no filler.

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?

With an output schema, full parameter documentation and mutation annotations, the description closes the remaining gap an agent would otherwise miss: the privacy default and the channel-connection prerequisite before calling.

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 coverage is 100% and each parameter is documented (render_id vs video_path, visibility enum, tag/title limits), so the schema does the heavy lifting. The description only echoes the visibility default, adding nothing beyond the structured fields; 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 ('Upload a finished render to the workspace's connected YouTube channel') plus the underlying API, which clearly separates it from siblings like grok_generate_video, grok_stitch and grok_render_status.

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?

Says to use it on a finished render and flags that visibility defaults to private, instructing the agent to choose unlisted/public deliberately. It also gives a hard prerequisite (channel connected in admin → Grok Boost), though it never names an alternative sibling for the not-yet-rendered case.

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

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