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 TikTok and YouTube it asks the platform for the processing status and returns the public link once there is one. 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.
brand_idNoBrand whose account published it; omit for the default brand.
platformYesPlatform of the post, e.g. "tiktok".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / brand_id
      Added value: +{
+  "description": "Brand whose account published it; omit for the default brand.",
+  "type": "string"
+}
  2. 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."
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: for TikTok/YouTube it queries the platform for processing status and returns the public link once available; for immediate-publish networks it returns 'published' and the link where the id allows it, including private Telegram channels via t.me/c/<channel>/<message>. This goes beyond the 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?

The description is a single, information-dense paragraph. It front-loads the core purpose and then adds platform-specific details. It could be slightly more structured (e.g., separating the general behavior from platform-specific notes), but it earns its length with useful distinctions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only status-checking tool with 100% schema coverage and no output schema, the description is largely complete. It explains what the tool returns (status and link), how it behaves per platform, and the meaning of the id parameter. It doesn't describe the exact shape of the response, but without an output schema that's a minor gap.

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 adds context about the 'id' being the post id returned at publish time and explains platform-specific behavior, but it doesn't add much beyond the schema for parameter semantics. Baseline 3 is appropriate.

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 clearly states the tool's function: it returns the status and link of a published post, keyed by platform and post id. It distinguishes itself from sibling tools like post_to_social and schedule_post by focusing on retrieval of status/link for already-published posts.

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 explains when to use this tool: to check the status and link of a published post, and it differentiates behavior by platform (TikTok/YouTube vs immediate-publish networks). It doesn't explicitly state when not to use it or name alternatives, but the context is clear enough for an agent to select it over publishing/scheduling tools.

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