Skip to main content
Glama

Delete page data entries

delete_page_data
Destructive

Delete entries and visitors' uploaded files of one list for good: by docIds, by fileIds, everything created between after and before (one bound is enough), or all. It cannot be undone; meant to be confirmed 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": {
      "collection": "<collection>"
    },
    "name": "delete_page_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
allNotrue = every entry and uploaded file of the list
afterNo
beforeNoISO 8601 time; a range deletes entries and uploaded files alike
docIdsNo1-20 entry ids
fileIdsNo1-20 file ids
manageUrlNoManagement link; replaces namespace, id and ownerToken
namespaceNo
collectionYes
ownerTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / after / description
      Removed value: -"ISO 8601 time: entries created after it"
    • addedInput schema / properties / all
      Added value: +{
      +  "description": "true = every entry and uploaded file of the list",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / before / description
      Previous value: -"ISO 8601 time: entries created before it"New value: +"ISO 8601 time; a range deletes entries and uploaded files alike"
    • removedInput schema / properties / collection / description
      Removed value: -"List (collection) name"
    • changedInput schema / properties / docIds / description
      Previous value: -"Entry ids from the listing, 1-20; instead of a time range"New value: +"1-20 entry ids"
    • addedInput schema / properties / fileIds
      Added value: +{
      +  "description": "1-20 file ids",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 20,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • removedInput schema / properties / id / description
      Removed value: -"Publication ID"
    • changedInput schema / properties / manageUrl / description
      Previous value: -"The page's private management link (https://brewpage.app/manage/...#k=...); stands in for namespace, id and ownerToken."New value: +"Management link; replaces namespace, id and ownerToken"
    • removedInput schema / properties / namespace / description
      Removed value: -"Publication namespace"
    • removedInput schema / properties / ownerToken / description
      Removed value: -"Owner token from create. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's main added value is widening the blast radius: uploaded files are deleted alongside entries, time ranges hit both, and the operation is irreversible and should be user-confirmed. It does not cover permissions, authentication, or what happens with overlapping selectors.

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: verb first, then the selector enumeration, then the irreversibility warning last where it lands hardest. No filler, and the colon list keeps four alternatives scannable.

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 10-parameter destructive tool with no output schema, the description covers the essentials an agent needs before calling: what is destroyed, that it is permanent, and that user confirmation is expected. Remaining gaps — return value, selector precedence, and auth via ownerToken/manageUrl — are minor for a delete 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?

With only 50% schema description coverage across 10 parameters, the description does real work: it explains that docIds and fileIds are alternative selectors, that after/before can be used with just one bound, and that 'all' wipes everything. The required `collection` parameter and the id/manageUrl/namespace/ownerToken group are left unexplained, though manageUrl's own schema description carries it.

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 (delete) and resource (entries plus visitors' uploaded files of one list), then enumerates the four selection modes (docIds, fileIds, after/before, all). This is enough to distinguish it from set_page_data/get_page_data and from delete_resource, which operates on a different resource.

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?

Gives clear operational context — 'meant to be confirmed with the user first' — and explains that 'one bound is enough' for time ranges, which an agent would otherwise have to guess. It stops short of naming when to prefer a sibling tool (e.g. delete_resource) or what to do if multiple selectors are supplied.

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.