Skip to main content
Glama
Sign In
brewpage-mcp

brewpage-mcp

by kochetkov-ma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete publication

delete_resource
Destructive

Delete a BrewPage resource—HTML page, site, KV store, JSON document, or file—using its owner token and required type, namespace, and ID.

Instructions

Delete a BrewPage resource (HTML page, site, KV store, JSON document, or file) using the owner token.

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
idYesResource ID
typeYesResource type to delete
namespaceYesResource namespace
ownerTokenNoOwner token from create. Default: env BREWPAGE_OWNER_TOKEN (local server only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.3
    • 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)."
  2. Changed2 schema fields changedv1.15.0
    • 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
  3. Changed3 schema fields changedv1.13.0
    • changedInput schema / properties / ownerToken / description
      Previous value: -"Owner token received when the resource was created"New value: +"Owner token from create. Default: BREWPAGE_OWNER_TOKEN."
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "html",
-  "kv",
-  "json",
-  "file"
-]New value: +[
+  "html",
+  "site",
+  "kv",
+  "json",
+  "file"
+]
    • changedInput schema / required
      Previous value: -[
-  "type",
-  "namespace",
-  "id",
-  "ownerToken"
-]New value: +[
+  "type",
+  "namespace",
+  "id"
+]
  4. First observedv0.1.0

TDQS

A3.5/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. The description usefully adds that an owner token is required for the operation, but says nothing about whether deletion is permanent, whether deleting a site cascades to its pages/files, or what failure looks like on a bad token — meaningful gaps for a destructive mutation.

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?

A single front-loaded sentence with the action, the resource scope, and the auth requirement; no filler and nothing buried.

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

Completeness3/5

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

There is no output schema and the tool is destructive, so the description should convey consequences — permanence, cascade behavior, and whether a confirmation is returned. It covers the auth prerequisite but leaves those behavioral facts unstated, which is adequate but not complete for a delete 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%, so type, namespace, id and ownerToken are all documented in the schema, including the env-var default for ownerToken. The description only echoes the token requirement and the resource-type list, adding essentially no semantics 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?

Specific verb (delete) plus the exact resource family, with the five resource kinds enumerated to match the schema's enum. Deletion is unambiguous against siblings like update_html or publish_site, so an agent can pick it without opening the schema.

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?

The description never says when to delete versus safer alternatives already in the sibling set, such as set_visibility to unlist a page or update_html to replace content. There is also no when-not-to-use or irreversibility warning, leaving selection guidance to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools