Mark

Request Changes or Reject

review_post

Destructive

Sends a post back with decision: changes_requested plus a note, or rejects it (rejected, final). Needs the current rev. To approve, use approve_posts. On a channel set to admins only, only workspace admins can decide; anyone else is refused. A rejected post will not publish. Requesting changes unlocks the draft for editing. Rejecting 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: get_post, approve_posts, comment_on_post.

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>",
      "rev": "<rev>",
      "decision": "<decision>",
      "note": "<note>"
    },
    "name": "review_post"
  }
}

Input Schema

Name	Required	Description
`rev`	Yes	Current rev from get_post.
`note`	Yes	What needs to change, or why it is rejected.
`postId`	Yes	Post id.
`decision`	Yes	changes_requested sends it back; rejected is final.

Output Schema

Name	Required	Description
`appUrl`	Yes
`postId`	Yes
`decision`	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?

Goes well past the destructiveHint=true annotation: it explains that a rejected post will not publish, that requesting changes unlocks the draft for editing, and that rejecting a website post may delete the CMS preview draft, with a documented fallback (cmsPreview plus the review note) when deletion isn't possible. That is exactly the consequence detail an agent needs before an irreversible action.

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-loaded with the action and the decision, and the alternative tool comes early. The CMS-preview sentence is long and tangled ('deletes that preview draft when Mark may; otherwise cmsPreview says...'), costing some clarity, though every clause carries real information.

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?

With an output schema present, the description needn't explain return values, and it covers permissions, side effects, the non-publish guarantee, and the failure/fallback state. Nothing an agent needs in order to call this safely is missing.

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?

Schema coverage is 100%, so all four parameters are already documented, including the decision enum meanings. The description only reinforces that the rev must be current, which largely repeats the schema's 'Current rev from get_post' — baseline 3 is appropriate.

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 (sends a post back / rejects) and the exact decision vocabulary (changes_requested, rejected-final), immediately distinguishing it from the approve path. An agent can identify the operation without opening the 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?

Explicitly routes the approve case to approve_posts, and the 'Related:' line names get_post (for the rev), comment_on_post and approve_posts as the adjacent tools. It also states the refusal condition on admins-only channels, so the agent knows a failure mode before calling.

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?