Skip to main content
Glama

Reject a hosted page

reject-hosted-page
Destructive

Reject a hosted page with a reason and close its topic, so discovery will not propose it again. A live page starts retiring, which only an account owner can do. request-hosted-page-regeneration keeps the topic instead. 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>",
      "reason": "<reason>"
    },
    "name": "reject-hosted-page"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy it was rejected. Recorded on the page and the gap.
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.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds material context beyond them: a live page enters a retiring state rather than vanishing, the operation requires account-owner privileges and a user-tied write credential, and confirmation should precede the call. That is exactly the risk/permission profile an agent needs before a destructive write.

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?

Four short sentences, each carrying distinct load: effect, state transition/permission, alternative, credential and confirmation requirements. The core action and its consequence are front-loaded with zero filler.

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 destructive write with no output schema, the description covers the action, its side effects, the permission model, the safer alternative, and the confirmation requirement. An agent has everything needed to decide and call correctly.

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%, and both parameters are already documented in the schema (reason recorded on page and gap; page_id sourced from list-hosted-pages). The description mentions 'with a reason' but adds no format, length, or sourcing detail beyond the structured fields, 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 specific verb and resource ('Reject a hosted page') plus the two downstream effects: closing the topic and preventing discovery from proposing it again. It explicitly names a sibling (request-hosted-page-regeneration) as the non-destructive counterpart, so an agent can separate it from nearby tools like retire-hosted-page without opening schemas.

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?

Gives explicit when/when-not routing: use this to permanently reject, use request-hosted-page-regeneration to keep the topic. It also states prerequisites ('only an account owner can do', 'Needs a user-tied write credential') and a procedural guard ('Confirm with the user 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