Skip to main content
Glama

brochure_unpublish

Idempotent

Take your brochure off its public address and the directory (it is kept, with its versions; publish again at any time). archive true keeps it for the record and never publishes it again.

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": {
      "slug": "<slug>"
    },
    "name": "brochure_unpublish"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesthe brochure's address
archiveNokeep for the record, never publish again

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, and the description adds real substance beyond that: the brochure and its versions are retained and can be republished, while archive=true is a permanent, non-reversible retirement. It does not address permissions or error behavior for already-unpublished brochures, so not a 5.

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?

Two compact sentences, front-loaded with the primary effect before the archive caveat. The parenthetical is slightly dense but every clause carries information about state or reversibility.

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 two-parameter, non-destructive state-change tool with full annotation coverage and no output schema, the description covers the state transition, what is retained, reversibility, and the irreversible archive variant. Nothing an agent needs in order to call it 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 slug and archive are already documented, and the description's phrasing for archive closely mirrors the schema text ('keep for the record, never publish again'). The added nuance is that the non-archive path preserves versions and allows republishing, which is modest value on top of a fully documented schema.

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 ('Take your brochure off its public address and the directory') and names the concrete effects, so it is unmistakable against siblings like brochure_publish or brochure_update. The parenthetical clarifies what is preserved, which further pins down the operation's scope.

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?

Clearly establishes the context for use (removing a brochure from public reach and the directory) and signals the reversible path with 'publish again at any time'. It does not explicitly state when to prefer brochure_update or brochure_publish instead, so it stops short of full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources