Skip to main content
Glama

Delete Upload Tool

delete_upload
DestructiveIdempotent

Delete an Upload and its file. Only call this when the user asks, or to free storage they agreed to free. Images already rendered with it keep working; its url stops working, so markup that still uses it renders without the photo.

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": {
      "upload_id": "<upload_id>"
    },
    "name": "delete_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
upload_idYesupload_id from create_upload or list_uploads.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description goes further by explaining the blast radius — rendered images survive, the URL stops resolving, and existing markup degrades to no photo. That is concrete consequence information an agent cannot get from annotations or schema.

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?

Three short sentences: the action first, the usage gate second, the consequences third. Every clause carries information and nothing is repeated from the schema or annotations.

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 one-parameter destructive tool with no output schema, the definition covers what is deleted, when it may be called, and what breaks afterward. Nothing an agent needs to call it correctly or explain the result to a user is missing.

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 the single parameter already carries "upload_id from create_upload or list_uploads." The description adds no format, sourcing, or validation meaning beyond that, so the 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?

The description gives a specific verb and resource ("Delete an Upload and its file") plus the scope of deletion — both the record and the underlying file. That distinguishes it from sibling mutations like delete_brand or set_brand without the agent needing to open any schema.

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?

It states an explicit precondition: "Only call this when the user asks, or to free storage they agreed to free," which is a real when-to-use gate with a consent qualifier. It does not name an alternative tool, but no obvious sibling performs the same de-duplication or cleanup function, so the missing exclusion is minor.

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