Skip to main content
Glama

Unpublish site

unpublish_site
Destructive

Take a site offline. Pages and data are kept; unused hosting time is not refunded.

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

Input Schema

NameRequiredDescriptionDefault
siteYesSite slug (e.g. "kopitiam-muar") or id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new context beyond the annotations: content is preserved (so the unpublish is reversible) and billing continues (no refund for unused hosting time), which an agent needs in order to warn a user before proceeding.

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 with zero filler: the action first, the consequence second. Every clause carries decision-relevant information, and nothing could be removed without losing meaning.

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 destructive single-parameter tool with no output schema, the description covers the two consequences an agent most needs (data retention and no refund). It leaves open what state the site is left in and whether custom domains or Komers stores remain active, which would be useful for a destructive operation.

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% for the single "site" parameter, including slug format and id acceptance, so the schema carries the parameter burden. The description adds nothing about how the site is identified, which is acceptable at this level of coverage and leaves the baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Take a site offline" names a specific verb and resource, and "Pages and data are kept" implicitly separates it from delete_site, which is in the sibling list. It does not explicitly name publish_site or delete_site as counterparts, so an agent still has to infer the boundary, but the operation itself is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The retention clause hints at when this is preferable to deletion, and the effect is scoped to a single site, which provides implied usage context. There is no explicit "use this instead of X" statement, no mention of the reverse operation (publish_site), and no prerequisites such as required ownership or confirmation.

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