Skip to main content
Glama

unpublish_entry

Revert a published entry to draft status to hide it from the live site while keeping the content editable. Use this to temporarily remove content without deleting it.

Instructions

Revert a published entry to draft status — removes it from the live website but keeps the content for editing. Use when the user wants to temporarily hide content without deleting it.

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": {
      "content_type": "<content_type>"
    },
    "name": "unpublish_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoLocale code
document_idNoDocument ID (required for collection types)
content_typeYesContent type UID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well by stating the main side effect: removal from the live website while preserving content for editing. It does not mention permissions, error behavior for already-draft entries, or authentication needs, which leaves some gaps but the core behavior is disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly written sentences, front-loaded with the core action and effect. Every phrase contributes to understanding the operation.

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 a simple mutation tool with a fully documented schema and no output schema, the description gives enough context to call it correctly. Minor gaps remain around preconditions and response behavior, but they are not substantial for this complexity level.

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 description coverage is 100%, so the input schema already documents all three parameters. The description adds no parameter-specific meaning beyond the schema, matching the baseline for high 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 and resource: reverting a published entry to draft, removing it from the live website while keeping content editable. It also implicitly distinguishes from delete_entry by noting the content is kept, so an agent can differentiate it from sibling tools.

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 a clear usage condition: when the user wants to temporarily hide content without deleting it. It does not name alternative tools or explicitly describe when not to use it, but the guidance is sufficient for correct selection.

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