Mark

Unpublish Post

unpublish_post

Destructive

Takes a published blog, FAQ or competitor page down from the website CMS and keeps the post in Mark. Workspace admins only. Mark unpublishes the page, reads it back, and only then records taken_down. The CMS document stays, so approving the post again updates the same page. Pass an optional reason stored on the post. Refused when the page is not live, the collection has no drafts, or the unpublish cannot be confirmed. Never returns API keys. Related: get_post, delete_post, approve_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": "unpublish_post"
  }
}

Input Schema

Name	Required	Description	Default
`postId`	Yes	The published website post whose CMS page to take down.
`reason`	No	Optional note stored on the post and the take-down record.

Output Schema

Name	Required	Description	Default
`state`	Yes
`postId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructive=true, readOnly=false, idempotent=false, openWorld=true. The description adds genuinely useful non-obvious behavior beyond that: the read-back verification before recording taken_down, the fact that the CMS document survives so re-approval reuses the same page, and the three refusal conditions. Minor deduction for the boilerplate 'Never returns API keys' which is irrelevant here.

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 packs failure semantics into a compact block; nearly every sentence earns its place. The closing 'Never returns API keys' sentence is unsupported boilerplate that dilutes an otherwise tight definition.

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, and the description still covers the authorization requirement, side effects, reversibility, and refusal cases for a destructive mutation. Nothing an agent needs in order to call this correctly 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 both parameters are already documented, and the description only restates the optional reason ('stored on the post'). No additional format, constraint, or identifier guidance is contributed beyond the schema baseline.

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 ('takes a published blog, FAQ or competitor page down from the website CMS') and adds the crucial qualifier that the post stays in Mark, which is what distinguishes it from delete_post and archive_post. An agent can tell what this does 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 Guidelines4/5

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

Names the precondition ('Workspace admins only') and the refusal conditions ('not live', 'collection has no drafts', 'unpublish cannot be confirmed'), and points at related tools. It gives clear context but never explicitly states when to prefer this over approve_posts/delete_post, leaving the routing inference to the agent.

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?