Skip to main content
Glama

Broadcast

by io.github.taraxe
OverviewDiscussionsAdmin

Update a post

update_post

Edits a draft, review or scheduled post: text, link, hashtags, first comment, media, targets, date or status. Only the fields given are changed. Use it instead of schedule_post to fix or reschedule an existing post (no duplicate is created), and instead of cancel_post when the post should still go out. Setting status "scheduled" publishes without approval and needs the publish scope, so only do it when the user asked. A published post cannot be edited.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesId of the post to edit, from get_schedule or schedule_post.
bodyNoMain text of the post. Per-network overrides go in `overrides`.
linkNoLink appended after the text (becomes a preview card on Bluesky, Facebook and LinkedIn without media).
mediaNoImages (up to 10 for most networks) or one video. Not both.
repeatNoPublishes the post again every day, week or month at the same time (Europe/Paris), counted from scheduledAt: once an occurrence goes out, the next one is created with the same content. null stops the series. TikTok settings chosen in the app apply to every occurrence.
statusNodraft: saved without a date. review (default when scheduledAt is set): waits for an approval in the app. scheduled: published automatically at scheduledAt, without approval (needs the publish scope); with scheduledAt "now" it goes out within a minute.
accountsNoTarget account ids (see GET /accounts / list_accounts).
hashtagsNoHashtags appended on their own line, with or without the leading #.
overridesNoText replacing `body` for one network, keyed by account id or platform name (e.g. a shorter text for x).
platformsNoAlternative to `accounts`: every connected account of these networks.
scheduledAtNoISO 8601 date-time with offset (e.g. 2026-10-14T09:00:00+02:00), or "now". Required for status review and scheduled.
firstCommentNoOptional reply Broadcast posts under the post right after it goes out, from the same account (e.g. the link, kept out of the post on LinkedIn, or the rest of a thread). Only on x, bluesky, linkedin, threads, facebook and instagram; ignored elsewhere. Limits: 280 on x (links count 23), 300 on bluesky, 1250 elsewhere. On X it costs credits like one more post. If it fails, the post stays published and the target's comment.error says why.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / firstComment / description
      Previous value: -"Optional reply Broadcast posts under the post right after it goes out, from the same account (e.g. the link, kept out of the post on LinkedIn, or the rest of a thread). Only on x, bluesky and linkedin; ignored elsewhere. Limits: 280 on x (links count 23), 300 on bluesky, 1250 on linkedin. On X it costs credits like one more post. If it fails, the post stays published and the target's comment.error says why."New value: +"Optional reply Broadcast posts under the post right after it goes out, from the same account (e.g. the link, kept out of the post on LinkedIn, or the rest of a thread). Only on x, bluesky, linkedin, threads, facebook and instagram; ignored elsewhere. Limits: 280 on x (links count 23), 300 on bluesky, 1250 elsewhere. On X it costs credits like one more post. If it fails, the post stays published and the target's comment.error says why."
    • changedInput schema / properties / platforms / items / enum
      Previous value: -[
-  "bluesky",
-  "x",
-  "facebook",
-  "instagram",
-  "tiktok",
-  "linkedin",
-  "mastodon"
-]New value: +[
+  "bluesky",
+  "x",
+  "facebook",
+  "instagram",
+  "tiktok",
+  "linkedin",
+  "mastodon",
+  "threads"
+]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses real behavioral traits: partial-update semantics ('Only the fields given are changed'), the publish-scope authorization requirement, that 'scheduled' publishes without approval, and the immutability of already-published posts. No contradiction with annotations.

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?

Front-loaded with scope and editable fields, then routing, then caveats — no filler sentences. The second sentence packs two alternative-tool conditions into one long clause, which is slightly dense but each clause carries needed information.

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 12 parameters, nested media objects, 100% schema coverage and annotations present, the description supplies exactly the missing behavioral layer: partial update, permission scope, publish side effects, and published-post limits. No output schema exists, so return values need not be explained.

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 description coverage is 100%, so the baseline is 3; the description still adds value with the partial-update rule ('Only the fields given are changed') and by grouping which fields are editable. It does not add syntax or per-field nuance beyond what the schema already documents.

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?

The opening sentence names a specific verb ('Edits') and enumerates the editable fields (text, link, hashtags, first comment, media, targets, date, status), immediately telling an agent what the tool covers. It also scopes which post states are editable (draft, review, scheduled), which no sibling duplicates.

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?

It explicitly routes the agent: use this instead of schedule_post to fix/reschedule (no duplicate created), and instead of cancel_post when the post should still go out. It also adds a when-not condition ('A published post cannot be edited') and a caution about status 'scheduled' publishing without approval.

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