Skip to main content
Glama

delete_asset

Destructive

Delete a file attached to a page by providing the page ID or path and filename, with guarded deletion that prevents removing others' changes.

Instructions

Delete a file attached to a page.

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": "<page>",
      "filename": "<filename>"
    },
    "name": "delete_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesPage id or path
filenameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether deletion is permanent, whether the filename is relative to the page, or what happens if the asset is missing — the exact context a destructive tool needs.

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 front-loaded sentence with zero filler. It is efficient, though the terseness comes at the cost of the behavioral and parameter detail noted elsewhere.

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 an irreversible mutation with no output schema and half the parameters undocumented, the definition is too thin — an agent cannot tell the scope of what gets destroyed or how to recover from a failed delete.

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

Parameters2/5

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

Schema coverage is only 50%: 'page' is documented as id or path, but 'filename' has no description at all. The description does not clarify filename semantics (basename only? path prefix? case sensitivity?) or how the two parameters combine, so the coverage gap is left unfilled.

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?

States a specific verb and resource: delete a file attached to a page. The phrase 'attached to a page' distinguishes it from delete_page and from the write_*_asset siblings that create or rename assets, though no sibling is named explicitly.

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 guidance on when to use this versus delete_page or the asset write tools, no prerequisite that the attachment must exist, and no note on whether the owning page survives the deletion.

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