Postly MCP

Delete Post

postly_delete_post

Destructive

Permanently removes only the post in Postly. Does not delete or recall live content on any social platform. For live removal, use Delete on Platforms in the dashboard where supported before deleting the post, or remove content directly on the platform. Requires a Postly post ID, not a provider post ID.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`post_id`	Yes	Postly post ID.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`code`	No
`data`	No
`prompt`	No
`status`	No
`message`	No
`next_steps`	No
`post_mutated`	No
`agent_guidance`	No
`ready_platforms`	No
`blocked_platforms`	No
`requires_user_input`	No
`retry_after_seconds`	No
`media_upload_results`	No
`missing_requirements`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 29, 2026
- addedOutput schema / properties / media_upload_results
```
Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / post_mutated
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / retry_after_seconds
```
Added value: +{
+  "type": "integer"
+}
```

Changed8 schema fields changedJun 12, 2026

addedOutput schema / properties / agent_guidance
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / blocked_platforms

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / missing_requirements

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / next_steps

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / prompt
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / ready_platforms

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / requires_user_input
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / status
```
Added value: +{
+  "type": "string"
+}
```

First observedMay 19, 2026

TDQS

A4.5/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is largely covered structurally. The description adds genuinely useful scope context — that deletion is Postly-only and does not recall live platform content — but a 'destination' scope note is the main addition beyond the annotation set.

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?

Three sentences, each doing distinct work: what gets deleted, what does not, and what ID is required. The scope constraint and alternative path are front-loaded rather than buried.

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?

Output schema exists, so return values need no explanation. For a destructive single-parameter tool, the description covers scope, irreversibility implication, prerequisite ID type, and the alternative path — nothing an agent needs to invoke correctly is missing.

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% with a single clearly described parameter, so the baseline is 3. The description earns above baseline by disambiguating the identifier: 'Requires a Postly post ID, not a provider post ID,' which prevents an agent from passing the wrong ID namespace.

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?

States a specific verb (delete) and resource (post), and immediately scopes it: 'Permanently removes only the post in Postly.' This separates it from siblings like postly_update_post and from any platform-level removal, so an agent can distinguish it without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent when not to expect this tool to work (live platform content is untouched) and routes to alternatives ('use Delete on Platforms in the dashboard... or remove content directly on the platform'). It also states the required prerequisite ID type, which prevents a common wrong invocation.

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

All Postly MCP 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?