Skip to main content
Glama

Retire a hosted page

retire-hosted-page
Destructive

Take a live page off the customer's domain. Without a redirect the URL answers 410, which tells an answer engine it is gone rather than missing. With one it 301s to another page already live on the same domain. Requires the account owner. Needs a user-tied write credential. Confirm with the user first.

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": {
      "page_id": "<page_id>"
    },
    "name": "retire-hosted-page"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYesHosted page ID from list-hosted-pages
redirect_to_slugNoSlug of a page already live on the same domain

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / page_id / description
      Previous value: -"Hosted page ID"New value: +"Hosted page ID from list-hosted-pages"
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / page_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description adds real behavioral detail beyond them: the URL serves 410 without a redirect and 301 with one, and the target must already be live on the same domain. It also discloses the authorization requirements (account owner, user-tied write credential) and a confirmation obligation, which an agent cannot infer from annotations.

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?

Five short sentences, front-loaded with the action, then consequences, then prerequisites, then the safety instruction. No filler and every sentence carries information an agent needs before calling.

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 two-parameter tool with no output schema, the description covers effect on the URL, permissions, and confirmation. The one gap is reversibility: it never says whether the page record survives retirement or can be restored, which matters for a destructiveHint=true operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds semantics beyond the schema: redirect_to_slug is optional and changes the URL's response to 301, and the target must already be live on the same domain. It does not elaborate on page_id beyond the schema's own note.

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?

"Take a live page off the customer's domain" gives a specific verb and resource, and the following sentences explain the two retirement modes (410 vs 301). This clearly separates it from sibling read tools (get-hosted-page, list-hosted-pages) and from reject-hosted-page/request-hosted-page-regeneration, which operate on unpublished pages.

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 states the decision point that selects the two modes (with vs without redirect) and gives prerequisites: account owner, user-tied write credential, and "Confirm with the user first." It stops short of explicitly naming an alternative tool for the delete-vs-redirect choice, but the operating conditions are unambiguous.

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