Skip to main content
Glama

Siren

by ai.mysiren
OverviewDiscussionsAdmin

post_run

Destructive

Post a finished run's assets to the workspace's CONNECTED SOCIAL ACCOUNT. This is live, public distribution on the customer's channel — always confirm with the user before calling. Only works if the grant was authorised with posting allowed. Pass caption to own the words; it goes out verbatim. The call queues the post behind a short publish window (about two minutes, cancellable) rather than firing inline: poll get_run after that and read posts[].url for the live permalink and the caption that went out.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_idYesThe run id returned by create_campaign, render_asset, or list_runs.
captionNoOptional caption for this publish; goes out verbatim. Omit and Siren writes it.
platformNoConnected channel to post to: x, instagram, tiktok, linkedin, or youtube.x

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / caption
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional caption for this publish; goes out verbatim. Omit and Siren writes it."
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / platform / description
      Added value: +"Connected channel to post to: x, instagram, tiktok, linkedin, or youtube."
    • addedInput schema / properties / run_id / description
      Added value: +"The run id returned by create_campaign, render_asset, or list_runs."
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

It clearly discloses the external, public nature of the action, the authorization prerequisite, the queued ~two-minute cancellable publish window, and the exact polling path to the live permalink. This goes well beyond what the annotations (destructiveHint/openWorldHint) already convey.

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?

Four sentences, front-loaded with the highest-stakes fact (live public distribution), followed only by necessary operational constraints and outcomes. No filler or redundant restatement of the tool name.

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?

The description covers the external effect, user confirmation, authorization, queue behavior, cancellation, and the polling path to the output permalink. Since an output schema exists, it need not restate return values, and nothing essential is missing.

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 all three parameters. The description's caption note mostly repeats the schema's 'verbatim / omit and Siren writes it' semantics, and it adds nothing new for run_id or platform. No meaningful value beyond structured input.

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 description names the action ('Post') and the resource ('a finished run's assets' to the workspace's CONNECTED SOCIAL ACCOUNT), making the tool's scope immediately clear. It also distinguishes itself from asset-generation or campaign tools by stressing that this is live, public distribution.

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?

The description gives strong context: confirm with the user before calling, only works if the grant allowed posting, and poll get_run afterward to observe the result. It does not explicitly contrast with sibling schedule_post for advance scheduling, so it stops short of a full when/when-not routing statement.

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

All Siren 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