Skip to main content
Glama

Publish a clip to several platforms

uploadpost_publish

Publish one clip to multiple social platforms in a single upload with a shared title and description; confirm before publishing because uploads cannot be undone.

Instructions

Send one clip to several platforms in a single upload: YouTube, TikTok, Instagram, Facebook, X, Threads, LinkedIn, Pinterest, Bluesky. The same title and description go everywhere unless the person asks otherwise. Uploads cannot be taken back, so get a clear yes 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": {
      "clip_id": "<clip_id>",
      "platforms": "<platforms>"
    },
    "name": "uploadpost_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
clip_idYesWhich clip to publish.
timezoneNoIANA name, e.g. America/Toronto.
platformsYese.g. ['youtube', 'tiktok', 'instagram'].
descriptionNo
add_to_queueNoNext free slot of their queue. Cannot be used with scheduled_date.
first_commentNo
scheduled_dateNoRFC 3339 WITH offset. Leave out to publish now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description does carry real weight by disclosing irreversibility and the confirmation requirement. However, it omits key behavior for a fan-out upload: whether the action is asynchronous, how to retrieve per-platform outcomes (the uploadpost_result/uploadpost_status siblings hint at this), and what happens on partial failure across nine platforms.

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?

Three short sentences with the capability front-loaded and the safety warning last, where it belongs. Little wasted wording, though the platform list consumes a full clause that could be compressed without losing selection value.

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 an 8-parameter, non-annotated, no-output-schema mutation that fans out to nine destinations, the definition should explain how results are obtained and what partial success looks like. It covers intent and safety but leaves the post-call workflow to inference from sibling names.

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 63%, so the schema documents several parameters itself. The description adds meaning only for title/description (shared across all platforms) and platforms (by listing destinations); it says nothing about scheduled_date, add_to_queue, timezone, first_comment, or the interaction between scheduling and queueing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource ("Send one clip to several platforms in a single upload") and enumerates every supported platform, so the agent knows exactly what the call does. It does not differentiate itself from look-alike siblings such as publish_plan, publish_plan_execute, or schedule_clips_execute, which an agent would need in order to choose correctly.

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

Usage Guidelines3/5

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

Implies an immediate one-shot publish and tells the agent to obtain explicit confirmation before firing, plus the default that one title/description is broadcast everywhere. It never states when to prefer this over the plan/execute or scheduling siblings, nor when not to use it (e.g. scheduled vs now), so routing guidance is only implied.

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