Skip to main content
Glama

Delete publication

delete_resource
Destructive

Delete a publication for good.

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": {
      "type": "<type>",
      "namespace": "<namespace>",
      "id": "<id>"
    },
    "name": "delete_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
typeYes
namespaceYes
ownerTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / id / description
      Removed value: -"Resource ID"
    • removedInput schema / properties / namespace / description
      Removed value: -"Resource namespace"
    • removedInput schema / properties / ownerToken / description
      Removed value: -"Owner token from create. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
    • removedInput schema / properties / type / description
      Removed value: -"Resource type to delete"
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "html",
      -  "site",
      -  "kv",
      -  "json",
      -  "file"
      -]New value: +[
      +  "html",
      +  "site",
      +  "file",
      +  "json",
      +  "kv"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / ownerToken / description
      Previous value: -"Owner token from create. Default: BREWPAGE_OWNER_TOKEN."New value: +"Owner token from create. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
  3. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  4. First observed

TDQS

C2.7/5.0
Behavior3/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 structurally. The description adds meaningful value with "for good", signaling permanence/irreversibility rather than a reversible unpublish. It says nothing about ownership/auth requirements (the ownerToken parameter) or side effects on related resources, which is a real gap for a destructive tool.

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?

A single seven-word sentence with zero filler and the permanence warning front-loaded. It is efficient but borders on under-specified rather than genuinely tight, given how much behavior it leaves unexplained.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter destructive mutation with no output schema and zero schema coverage, the definition is far too thin. It omits parameter meaning, auth requirements, and any notion of what a successful deletion returns or whether it fails on missing resources.

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

Parameters1/5

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

Schema description coverage is 0% across four parameters (id, type, namespace, ownerToken), and the description adds no meaning for any of them. It does not explain the type enum values (html, site, file, json, kv), what namespace scopes, or when ownerToken is required, so an agent gets no help on how to construct the call.

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?

The description gives a specific verb ("Delete") and resource ("publication"), plus a permanence qualifier ("for good") that hints at irreversibility. It does not differentiate from siblings such as make_private or delete_page_data, which could plausibly be confused with it, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no stated alternative. "For good" implicitly contrasts with some softer operation (e.g. make_private), but the agent must infer that; no prerequisites, confirmation requirements, or exclusions are given.

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.