postly_get_post_statusRetrieves the current publishing status and delivery counts for a specific Postly post.
| Name | Required | Description | Default |
|---|---|---|---|
| post_id | Yes | Postly post ID. |
| Name | Required | Description | Default |
|---|---|---|---|
| status | No | ||
| post_id | No | ||
| delivery_results | No | ||
| effective_status | No | ||
| draft_delivery_count | No | ||
| failed_delivery_count | No | ||
| published_delivery_count | No |
Changes observed during successful MCP inspections.
Output schema / properties / delivery_resultsAdded value: +{
+ "items": {
+ "type": "object"
+ },
+ "type": "array"
+}Output schema / properties / draft_delivery_countAdded value: +{
+ "type": "integer"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds the 'delivery counts' detail, but it does not disclose any additional behavioral traits such as response shape, latency, or relationship to analytics data.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence states exactly what is retrieved and for which resource. No filler or redundant restating of the title.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With one well-documented parameter, strong annotations, and an output schema present, the description is sufficient for an agent to invoke the tool. Nothing essential to the call itself is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the post_id parameter is already documented as 'Postly post ID.' The description adds no extra meaning beyond the schema, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a clear verb ('Retrieves') with a specific resource ('current publishing status and delivery counts for a specific Postly post'). It conveys what the tool does, but it does not explicitly distinguish it from siblings like postly_get_post or postly_get_post_analytics, leaving some potential ambiguity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives. It does not mention scenarios like checking after publishing, polling for delivery, or why one would choose this over postly_get_post_analytics or postly_get_publishing_activity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.