Delete file
uploadcare_delete_fileDestructive
Permanently deletes a file from the project. Destructive. REST API: DELETE /files/{uuid}/.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | File UUID to delete. |
uploadcare
by io.usefulapi
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Destructive annotation (destructiveHint=true) already indicates mutation. Description adds 'Permanently deletes' and 'Destructive' but no additional behavioral traits beyond what annotations provide. No contradiction.
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?
Two concise sentences with no wasted words. Action is front-loaded and immediately clear.
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 simple delete operation with one parameter and no output schema, the description covers all necessary context: permanence, destructiveness, and API endpoint reference.
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 for uuid is clear ('File UUID to delete'), and coverage is 100%. Description does not add extra meaning beyond the schema.
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?
Description clearly states 'Permanently deletes a file from the project' with a specific verb and resource. No sibling tool performs deletion, so it is well-differentiated.
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?
No explicit guidance on when to use this tool vs alternatives. Does not mention prerequisites (e.g., file existence) or conditions under which deletion is appropriate.
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.
TDQS
A3.9/5.0
Disambiguation5/5
Each tool targets a distinct resource and action (e.g., create webhook vs. delete file vs. get group). No two tools overlap in purpose, making it easy for an agent to select the correct one.
Naming Consistency5/5
All tools follow a consistent snake_case verb_noun pattern: uploadcare_create_webhook, uploadcare_delete_file, etc. This predictability helps agents infer tool functions from names.
Tool Count5/5
With 11 tools, the server covers key areas (files, groups, webhooks, project) without being overwhelming. The count is well-scoped for a file management service.
Completeness3/5
The tool set covers core file operations (get, delete, list, store, upload) but has gaps: missing update/delete for webhooks, create/delete for groups, and update for files. These omissions may force agents to use workarounds.