AutoPoster AI

Get Post Status

autoposter_get_post_status

Read-only

Checks delivery status of a post and returns live platform links/receipts once published.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`postId`	Yes	The post ID to query.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Post ID.
`state`	Yes	Current status: drafts, pending_approval, queued, posted, or failed.
`postLink`	No	Live URL link to the published post on the platform.
`postedAt`	No	ISO timestamp when the post was published.
`errorMessage`	No	Error message if post failed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "errorMessage": {
+      "description": "Error message if post failed.",
+      "type": "string"
+    },
+    "id": {
+      "description": "Post ID.",
+      "type": "string"
+    },
+    "postLink": {
+      "description": "Live URL link to the published post on the platform.",
+      "type": "string"
+    },
+    "postedAt": {
+      "description": "ISO timestamp when the post was published.",
+      "type": "string"
+    },
+    "state": {
+      "description": "Current status: drafts, pending_approval, queued, posted, or failed.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "state"
+  ],
+  "type": "object"
+}

First observedOct 7, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, so the safety profile is covered. The description adds useful timing context ('once published') for when links/receipts become available, but says nothing about caching, freshness, or polling behavior for posts still in flight.

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?

A single front-loaded sentence with zero filler. The operation and the result are both stated up front, and no sentence is wasted.

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?

With an output schema, annotations covering safety, and a fully documented single required parameter, the definition supplies enough for an agent to call it correctly. The only mild gap is that it does not clarify behavior for pending/failed posts, which would have been helpful for a status-check tool.

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?

There is one parameter with 100% schema description coverage ('The post ID to query.'), so the schema fully documents it. The description adds no extra meaning about the postId format or origin, which is the expected baseline when the schema does the work.

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 description names a specific verb and resource ('checks delivery status of a post') and adds the return payload ('live platform links/receipts once published'). It implicitly distinguishes itself from autoposter_get_post by focusing on delivery/publication state, but never names a sibling explicitly.

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?

Usage is only implied: an agent can infer this is the tool for post-delivery checks, but there is no explicit when-to-use, when-not-to-use, or alternative routing versus autoposter_get_post or autoposter_list_posts. No prerequisites or context conditions are stated.

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

All AutoPoster AI tools Inspect

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

Need Help?