Skip to main content
Glama

Send a hosted page back for a rewrite

request-hosted-page-regeneration
Destructive

Send a hosted page back to be rewritten, with a note on what to change. The topic stays queued; reject-hosted-page closes it instead. A live page starts retiring, because a draft cannot be served, and only an account owner can send back a live page. 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>",
      "note": "<note>"
    },
    "name": "request-hosted-page-regeneration"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYesWhat the rewrite should do differently.
page_idYesHosted page ID from list-hosted-pages

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?

Goes well beyond the destructiveHint/readOnlyHint annotations by disclosing the state transition (a live page starts retiring because a draft cannot be served), the permission requirement (account owner only), the credential type, and a human-confirmation protocol. This is exactly the operational context annotations cannot express.

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?

Four tight sentences, each carrying new information, with the action front-loaded and the sibling distinction placed early. The state-transition sentence is slightly compressed ('a live page starts retiring') but no sentence is wasted.

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 destructive mutation with no output schema, the description supplies everything an agent needs to call it safely: side effects, authorization constraints, required confirmation, and routing against the closest alternative. Nothing material 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 description coverage is 100%, so both page_id and note are already documented, including the note's purpose and length bounds. The description only paraphrases the note ('a note on what to change'), so baseline 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?

States a concrete verb+resource (send a hosted page back to be rewritten) plus the required accompanying note, and immediately contrasts it with reject-hosted-page (which closes the topic). An agent can distinguish it from the other hosted-page siblings (reject, retire, publish) without opening any schema.

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

Usage Guidelines5/5

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

Explicit alternative is named with the condition that selects it ('The topic stays queued; reject-hosted-page closes it instead'), and preconditions are given: only an account owner can send back a live page, a user-tied write credential is needed, and the user must confirm first.

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