Mark

Archive Post

archive_post

Idempotent

Takes a post out of the publish path so it will not go live. The post stays in the workspace; this is not a delete. Posts that are already live, queued to publish, or approved cannot be archived — they stay as they are. Archiving a post that is not a draft (in review, sent back, failed or missed) rejects it, so on a channel set to admins only (approverRole: approver) only workspace admins can archive it; drafts stay open to everyone. Calling it again on a post that will not publish is a no-op. Archiving a website post that sent a preview to its CMS deletes that preview draft when Mark may; otherwise cmsPreview says it is still in the CMS, where, and why, and so does the post's review note. Related: delete_post, review_post, search_posts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "postId": "<postId>"
    },
    "name": "archive_post"
  }
}

Input Schema

Name	Required	Description	Default
`note`	No	Optional reason stored on the post.
`postId`	Yes	The post to archive.

Output Schema

Name	Required	Description
`postId`	Yes
`status`	Yes
`outcome`	Yes
`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; translated: its translations are in the same page; unreachable: the CMS did not answer). Absent when the post had no preview.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026

changedOutput schema / properties / cmsPreview / description

Previous value: -"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."New value: +"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; translated: its translations are in the same page; unreachable: the CMS did not answer). Absent when the post had no preview."

changedOutput schema / properties / cmsPreview / oneOf

Previous value: -[
-  {
-    "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"
-  }
-]New value: +[
+  {
+    "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",
+          "translated",
+          "unreachable"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "outcome",
+      "previewUrl",
+      "reason"
+    ],
+    "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"
+    }
+  ]
+}

First observedOct 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description adds substantial behavior beyond the annotations: the post remains in the workspace, specific states block archiving, non-draft archiving rejects the post, permissions vary by approverRole, repeat calls are no-ops, and CMS preview drafts may be deleted with failure reasons exposed via cmsPreview and review note. These details are consistent with the non-destructive and idempotent annotations.

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 description is front-loaded with the core action and then covers necessary constraints and edge cases, so most sentences earn their place. It is dense and contains some long clauses around permissions and CMS preview behavior, but the length is largely justified by the tool's complexity.

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?

Given the annotations, output schema, and two-parameter schema, the description is complete enough for correct invocation. It covers state restrictions, permissions, idempotency, CMS preview side effects, and related tools, leaving no major behavioral gap for an agent.

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?

The schema has 100% description coverage for both parameters, including postId and the optional note reason, so the schema already carries parameter meaning. The description does not add syntax or format details for the parameters, which is acceptable given full schema coverage.

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?

The description states a specific action on a specific resource: it takes a post out of the publish path and explicitly says this is not a delete. It clearly differentiates archiving from deletion and from publishing states, so an agent can distinguish it from delete_post and related workflow tools.

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?

It gives explicit when/when-not guidance: already-live, queued-to-publish, and approved posts cannot be archived; non-draft posts are rejected and require admin permissions on restricted channels. It also notes repeat calls are no-ops and names related tools (delete_post, review_post, search_posts).

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?