Mark

Delete Post

delete_post

Destructive

Permanently deletes a post: a draft, one in review, one approved or scheduled, or a published one. An unpublished post's Zernio post is canceled and deleted first (for a website post, its pending CMS publish is withdrawn); if that fails, nothing changes. Its review history, comments and performance logs are deleted with it; tracking links stay and keep their clicks. External posts cannot be deleted. A website post's preview draft in its CMS is deleted first when Mark may; otherwise cmsPreview says it is still in the CMS, where, and why, so you can delete it there. Published posts are admins only; anyone else is refused. By default a published post is removed from Mark only and stays live (takenDown left_live with its liveUrl). With takeDown: true, Mark first deletes it from LinkedIn, X, Facebook, YouTube or Pinterest, or unpublishes a website page in its CMS and then deletes the page when Mark's key may (otherwise takenDown left_in_cms says where the draft stays). Instagram and TikTok posts can't be taken down by apps: takeDown is refused for them, so remove them in the app and delete with takeDown false. A failed take-down changes nothing: the post stays in Mark, still published, and the error names the platform and the fix. This cannot be undone. Related: archive_post, search_posts, save_post.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`postId`	Yes	The post to delete. Published posts need a workspace admin.
`takeDown`	No	Published posts only: also take it down from the platform or CMS first. Default false (remove from Mark only; it stays live). Refused for Instagram and TikTok.

Output Schema

TableJSON Schema

Name	Required	Description
`postId`	Yes
`status`	Yes
`outcome`	Yes
`takenDown`	No	A published post only: taken_down (deleted from the platform, or its CMS page deleted), left_in_cms (unpublished, but the page stays in the CMS as a draft at previewUrl, for the same reasons as cmsPreview), or left_live (removed from Mark only; still live at liveUrl).
`cmsPreview`	No	The post's preview draft in the website CMS: removed (Mark deleted it), or left_in_cms with its previewUrl and why (cannot_delete: Mark's API key may not delete it; edited: changed in the CMS; linked: a page that was in the CMS before Mark used it; live: a live page; unreachable: the CMS did not answer). Absent when the post had no preview.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 19, 2026

changedInput schema / properties / postId / description

Previous value: -"The post to delete. Published posts cannot be deleted."New value: +"The post to delete. Published posts need a workspace admin."

addedInput schema / properties / takeDown

Added value: +{
+  "description": "Published posts only: also take it down from the platform or CMS first. Default false (remove from Mark only; it stays live). Refused for Instagram and TikTok.",
+  "type": "boolean"
+}

addedOutput schema / properties / takenDown

Added value: +{
+  "description": "A published post only: taken_down (deleted from the platform, or its CMS page deleted), left_in_cms (unpublished, but the page stays in the CMS as a draft at previewUrl, for the same reasons as cmsPreview), or left_live (removed from Mark only; still live at liveUrl).",
+  "oneOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "outcome": {
+          "const": "taken_down",
+          "type": "string"
+        }
+      },
+      "required": [
+        "outcome"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "outcome": {
+          "const": "left_in_cms",
+          "type": "string"
+        },
+        "previewUrl": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "reason": {
+          "enum": [
+            "cannot_delete",
+            "edited",
+            "linked",
+            "live",
+            "unreachable"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "outcome",
+        "previewUrl",
+        "reason"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "liveUrl": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "outcome": {
+          "const": "left_live",
+          "type": "string"
+        }
+      },
+      "required": [
+        "liveUrl",
+        "outcome"
+      ],
+      "type": "object"
+    }
+  ]
+}

Changed1 schema field changedOct 17, 2026

addedOutput schema / properties / cmsPreview

Added value: +{
+  "description": "The post's preview draft in the website CMS: removed (Mark deleted it), or left_in_cms with its previewUrl and why (cannot_delete: Mark's API key may not delete it; edited: changed in the CMS; linked: a page that was in the CMS before Mark used it; live: a live page; unreachable: the CMS did not answer). Absent when the post had no preview.",
+  "oneOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "outcome": {
+          "const": "removed",
+          "type": "string"
+        }
+      },
+      "required": [
+        "outcome"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "outcome": {
+          "const": "left_in_cms",
+          "type": "string"
+        },
+        "previewUrl": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "reason": {
+          "enum": [
+            "cannot_delete",
+            "edited",
+            "linked",
+            "live",
+            "unreachable"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "outcome",
+        "previewUrl",
+        "reason"
+      ],
+      "type": "object"
+    }
+  ]
+}

Changed1 schema field changedOct 16, 2026

changedInput schema / properties / postId / description

Previous value: -"The draft to delete. Only unsent drafts can be deleted."New value: +"The post to delete. Published posts cannot be deleted."

First observedOct 1, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Far exceeds the annotations, which only mark it destructive/non-idempotent. It discloses what gets destroyed (review history, comments, performance logs; tracking links survive), the Zernio/CMS cancellation sequence, per-platform takeDown behavior, the Instagram/TikTok refusal, and the all-or-nothing failure semantics. This is exactly the irreversible-mutation context an agent needs.

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?

Front-loads the core action and the irreversible warning, and every paragraph maps to a distinct behavior (default delete, CMS preview, takeDown, failures). It is long and dense, but the length is justified by the tool's cross-platform complexity, with little filler.

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?

For a destructive, cross-platform tool with an output schema, the description covers the remaining burden: permissions, the takeDown matrix, failure modes and their error reporting, and the preview-draft edge case. Nothing an agent needs to invoke it safely 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%, so the schema already documents both parameters (baseline 3). The description adds real meaning beyond the schema: the default false behavior with the liveUrl outcome, the per-platform unpublish/delete sequence, and which platforms are refused.

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 and resource ('Permanently deletes a post') and immediately enumerates the valid post states, so an agent knows exactly what it operates on. It also explicitly contrasts with archive_post, so it is distinguishable from its closest sibling without opening either schema.

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?

Gives explicit when-to-use conditions (admin-only for published posts), when-not (external posts cannot be deleted; Instagram and TikTok cannot be taken down), and names alternatives (archive_post). The Related list routes the agent to the right siblings.

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

All Mark 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?