Skip to main content
Glama

PostWire

by io.github.Perufitlife
OverviewDiscussionsAdmin

Check a post's publishing status

get_post_status
Read-onlyIdempotent

Returns the status and link of a published post, by platform and the post id returned when it was published. For a post that is waiting for approval or scheduled, pass the id PostWire returned for it (platform can then be omitted): the status is pending_approval (with who was asked and the review link), rejected (with the reason), scheduled, or each network's result once it went out. For TikTok and YouTube it asks the platform for the processing status and returns the public link once there is one. For an Instagram video returned as "processing", pass the id it returned: the answer is processing, published (with its id and link) or failed (with the reason). For networks that publish immediately it returns status "published" and, where the id allows it, the post's link (Telegram channels, including private ones as t.me/c//; Bluesky; LinkedIn; Facebook).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe post id returned when it was published on that platform, or the id PostWire returned for a post waiting for approval or scheduled.
brand_idNoBrand whose account published it; omit for the default brand.
platformNoPlatform of the post, e.g. "tiktok". Can be omitted for a post waiting for approval or scheduled.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
-  "telegram",
-  "bluesky",
-  "mastodon",
-  "discord",
-  "tiktok",
-  "youtube",
-  "reddit",
-  "linkedin",
-  "facebook",
-  "instagram",
-  "x"
-]New value: +[
+  "telegram",
+  "bluesky",
+  "mastodon",
+  "discord",
+  "wordpress",
+  "devto",
+  "hashnode",
+  "slack",
+  "nostr",
+  "tiktok",
+  "youtube",
+  "reddit",
+  "linkedin",
+  "facebook",
+  "instagram",
+  "x"
+]
  2. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"The post id returned when it was published on that platform."New value: +"The post id returned when it was published on that platform, or the id PostWire returned for a post waiting for approval or scheduled."
    • changedInput schema / properties / platform / description
      Previous value: -"Platform of the post, e.g. \"tiktok\"."New value: +"Platform of the post, e.g. \"tiktok\". Can be omitted for a post waiting for approval or scheduled."
    • changedInput schema / required
      Previous value: -[
-  "platform",
-  "id"
-]New value: +[
+  "id"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
-  "telegram",
-  "bluesky",
-  "mastodon",
-  "discord",
-  "tiktok",
-  "youtube",
-  "reddit",
-  "linkedin",
-  "facebook",
-  "instagram"
-]New value: +[
+  "telegram",
+  "bluesky",
+  "mastodon",
+  "discord",
+  "tiktok",
+  "youtube",
+  "reddit",
+  "linkedin",
+  "facebook",
+  "instagram",
+  "x"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
-  "telegram",
-  "bluesky",
-  "mastodon",
-  "discord",
-  "tiktok",
-  "youtube",
-  "reddit",
-  "linkedin",
-  "facebook",
-  "instagram",
-  "x"
-]New value: +[
+  "telegram",
+  "bluesky",
+  "mastodon",
+  "discord",
+  "tiktok",
+  "youtube",
+  "reddit",
+  "linkedin",
+  "facebook",
+  "instagram"
+]
  5. Changed1 schema field changed
    • addedInput schema / properties / brand_id
      Added value: +{
+  "description": "Brand whose account published it; omit for the default brand.",
+  "type": "string"
+}
  6. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"The id returned by post_to_social for that platform."New value: +"The post id returned when it was published on that platform."
  7. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already establish readOnly, idempotent, non-destructive, but the description goes well beyond them: it enumerates the possible statuses (pending_approval, rejected, scheduled, processing, published, failed), explains that TikTok/YouTube trigger a platform-side processing poll, that Instagram may return 'processing' requiring a re-call, and that immediate-publish networks return the public link with channel-specific URL shapes. That is exactly the behavioral depth an agent needs for a polling-style read.

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?

It is front-loaded – purpose first, then per-scenario detail – and nearly every sentence carries platform-specific information that would otherwise be missing. It is one dense block rather than a scannable structure, which costs it the top mark, but there is little 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?

There is no output schema, so the description carries the full burden of explaining return values, and it does: it enumerates the possible status values, what accompanies each (review link, rejection reason, failure reason), and the link format per network. An agent can call this and interpret the response without further documentation.

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 the baseline is 3, but the description adds conditional logic the schema only hints at: 'platform can then be omitted' for approval/scheduled posts, the dual meaning of 'id' (platform post id vs. PostWire id), and the re-call pattern for Instagram videos returned as 'processing'. That materially clarifies how to populate the parameters in each case.

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?

The opening sentence gives a specific verb and resource: 'Returns the status and link of a published post, by platform and the post id.' That is unambiguous and clearly distinct from the performance-oriented sibling get_post_performance. It stops short of naming any sibling or stating exclusions, so it lands at 4 rather than 5.

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?

The description spends most of its length on scenario routing – which id to pass for pending/scheduled posts, for Instagram 'processing' videos, for TikTok/YouTube – which is genuinely useful invocation context. However, it never says when to reach for this tool instead of list_scheduled_posts, get_post_performance, or cancel_scheduled_post, and gives no when-not guidance. Implied usage only.

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

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