Skip to main content
Glama
Sign In

Broadcast

by io.github.taraxe
OverviewDiscussionsAdmin

Upload media from a URL

upload_media

Copies a public image (JPEG, PNG, WebP, GIF; 10 MB max) or video (MP4, MOV, WebM; 100 MB max) into Broadcast and returns its key. Give an image its alt text here: posts using the key send it. Call it before schedule_post or update_post whenever the post has media, then pass the key in media; a plain URL is not accepted there. Required for Instagram and TikTok, which refuse text-only posts.

Input Schema

NameRequiredDescriptionDefault
altNoAlternative text describing the image for people who cannot see it. Kept with the file: every post using this key without its own `alt` sends it (bluesky, mastodon, x, linkedin, threads, facebook, instagram).
urlYesPublic URL of an image (JPEG, PNG, WebP, GIF, 10 MB max) or video (MP4, MOV, WebM, 100 MB max) to copy into Broadcast.
sourceUrlNoOptional https address of the conversation or session making this call (for instance a Claude Code session link), shown as a link in the user's activity log. Omit it when unknown; never invent one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / alt / description
      Previous value: -"Alternative text for an image, read by screen readers on the networks that support it."New value: +"Alternative text describing the image for people who cannot see it. Kept with the file: every post using this key without its own `alt` sends it (bluesky, mastodon, x, linkedin, threads, facebook, instagram)."
  2. Changed1 schema field changed
    • addedInput schema / properties / sourceUrl
      Added value: +{
+  "description": "Optional https address of the conversation or session making this call (for instance a Claude Code session link), shown as a link in the user's activity log. Omit it when unknown; never invent one.",
+  "format": "uri",
+  "type": "string"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-idempotent, non-destructive mutation; the description adds real behavioral context beyond that: the URL is copied into Broadcast, the response carries a `key`, the key is what later calls accept, and alt text persists with the file. It does not say what happens on failure (unsupported host, oversized file) or whether re-uploading the same URL creates a duplicate, which matters given idempotentHint=false.

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?

Four sentences, front-loaded with the action and limits before the workflow rules, with no filler. The format/size list slightly duplicates the `url` schema description, a minor redundancy.

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?

No output schema exists, yet the description states the return value (`key`), the workflow position among siblings, and the platform-level requirement that motivates it. Combined with a fully documented schema, an agent has everything needed to invoke it correctly.

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?

Schema coverage is 100%, so baseline is 3, but the description adds cross-field meaning: `alt` is stored with the file and inherited by posts using the key, and `url` is a copy source rather than a reference. `sourceUrl` is left entirely to the schema, which is acceptable.

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 ('Copies a public image ... or video ... into Broadcast') and even the return value ('returns its `key`'), with concrete format and size bounds. It is clearly distinguishable from siblings like schedule_post and update_post, which it names as downstream consumers.

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 explicit sequencing ('Call it before schedule_post or update_post whenever the post has media'), a hard exclusion ('a plain URL is not accepted there'), and a platform precondition ('Required for Instagram and TikTok, which refuse text-only posts'). An agent has no inference left to make about when to call this.

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

All Broadcast toolsInspect
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