Skip to main content
Glama

Take a site offline

unpublish_site
DestructiveIdempotent

Takes a published site offline. The draft and saved versions are kept, and publish_site puts it back online.

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": {
      "site_id": "<site_id>"
    },
    "name": "unpublish_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site id from list_sites or create_site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds the genuinely useful qualifier that draft and saved versions survive the operation and that publish_site reverses it. It does not address what happens to live visitors, custom domains, or whether the unpublished state is reflected immediately, which would complete the picture.

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 short sentences, front-loaded with the action and followed by the state consequence and recovery path. No filler and nothing repeated from the title or annotations.

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 one-parameter toggle tool with rich annotations, the description covers what the action does, what is preserved, and how to undo it. The absence of an output schema and of any note about returned status or side effects on domains keeps it just short of fully complete.

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?

Only one parameter exists and the schema documents it at 100% coverage, including its provenance ('from list_sites or create_site'). The description adds nothing about site_id, so the baseline of 3 applies.

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?

Names a specific verb and resource ('Takes a published site offline') and immediately clarifies that the draft and saved versions are retained, which is exactly the detail that distinguishes it from a delete operation. An agent can tell this apart from delete_site or update_site without inspecting schemas.

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 names the complementary action explicitly ('publish_site puts it back online'), giving a clear use-and-reverse context. It stops short of stating when an agent should choose this over delete_site or when the site has never been published, so it is clear but not fully directive.

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