Antwork

delete_post

Destructive

Delete a post. Drafts and scheduled posts are removed; a published post is hidden but keeps its metrics history unless preserve_analytics=false.

post_ids deletes up to 50 with the same options in one call; each answers in posts, and one that fails does not stop the rest.

Args: post_id: The post ID to delete. delete_from_platforms: True also deletes it from every platform it was published to; a list of platform names limits that to those. TikTok has no delete API. Omitted, the live posts stay. preserve_analytics: Published posts only; defaults to true. workspace_id: Workspace ID or name. Optional if user has only one workspace. post_ids: Several posts to delete, instead of post_id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delete_post"
  }
}

Input Schema

Name	Required	Description
`context`	No	The user's underlying goal for this call, in one sentence without personal details. Used for product analytics only.
`post_id`	No
`post_ids`	No
`llm_model`	No	The model identifier of the calling assistant, or "unknown". Used for product analytics only.
`workspace_id`	No
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.
`preserve_analytics`	No
`delete_from_platforms`	No

Output Schema

Name	Required	Description	Default
`_mcp_instructions`	No	Server-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 9, 2026

addedInput schema / properties / post_id / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / post_id / default
```
Added value: +null
```
removedInput schema / properties / post_id / type
```
Removed value: -"string"
```

addedInput schema / properties / post_ids

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Post Ids"
+}

changedInput schema / required

Previous value: -[
-  "post_id"
-]New value: +[]

Changed1 schema field changedOct 26, 2026

changedInput schema / required

Previous value: -[
-  "post_id",
-  "context",
-  "llm_model"
-]New value: +[
+  "post_id"
+]

First observedOct 22, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond the destructiveHint=true annotation, the description discloses exactly what is destroyed versus hidden (drafts/scheduled removed, published posts only hidden), that metrics history survives by default, that TikTok has no delete API, and that batch deletions are partially tolerant of failure. This is unusually rich behavioral context for a destructive tool.

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 core semantics are front-loaded in the first two sentences, followed by a well-formatted Args block that maps one-to-one to parameters. Slightly long, but nearly every clause adds decision-relevant detail.

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 an 8-parameter destructive tool with an output schema, the definition covers the risky behaviors, batching, and per-parameter meaning well. Minor gaps remain around how results are keyed when only `post_id` is used and any permission prerequisites.

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 only 38%, and the description compensates by explaining the boolean-vs-list overload of `delete_from_platforms`, the published-only scope of `preserve_analytics`, the workspace_id optionality rule, and the post_id/post_ids exclusivity. The remaining analytics parameters (context, llm_model, conversation_id) are documented in the schema itself.

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 first sentence names a specific verb and resource ("Delete a post") and immediately qualifies what deletion means for each post state. An agent can distinguish this from update_post or delete_media by behavior, though no sibling is named explicitly.

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?

It gives clear context for choosing the batch path ("`post_ids` deletes up to 50 ... instead of post_id") and states the consequence of omitting `delete_from_platforms`. It stops short of explicit when-not-to-use guidance or pointing at sibling tools for related operations.

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

All Antwork 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.