Skip to main content
Glama
Sign In

Dock

by ai.trydock
OverviewDiscussionsAdmin

delete_file_upload

Delete a staged upload right away: pass the url a create_file_upload link returned, with the same workspace slug. Use it to revoke a staged url that was shared by mistake, or one you no longer need. Only a url from a create_file_upload link for this workspace is accepted; anything else is refused and nothing is deleted. A url that is already gone counts as deleted. Files already in a Files surface are not affected (use delete_file for those). Editor role required.

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": {
      "slug": "<slug>",
      "url": "<url>"
    },
    "name": "delete_file_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe `url` the `create_file_upload` link's curl returned.
slugYesThe workspace slug (bare or org-prefixed) the upload link was made for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses idempotent semantics ('A `url` that is already gone counts as deleted'), input validation behavior ('anything else is refused and nothing is deleted'), the required authorization level ('Editor role required'), and the scope of effect (nothing but the staged upload is touched). This is behavior an agent cannot infer from the schema.

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?

It is front-loaded with the action and the two parameters, then usage, then constraints, and every sentence carries information. Minor redundancy exists between the opening clause and the 'revoke it if shared by mistake' sentence, which restates the staged-share scenario.

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 two-parameter destructive tool with no annotations or output schema, the description covers preconditions, validation, idempotency, permissions, and post-condition behavior, so no output schema is needed to understand the result.

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?

Schema coverage is 100%, so both parameters are already documented, but the description adds real meaning: `url` must be one returned by a `create_file_upload` link, and `slug` must be the same workspace that link was made for, with cross-workspace values refused. The one small gap is that it does not clarify the 'bare or org-prefixed' slug forms the schema mentions.

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 opens with a specific verb and resource ('Delete a staged upload') and immediately pins the resource to a `url` returned by `create_file_upload`, which distinguishes it from the sibling `delete_file` (files in a Files surface) and from `create_file_upload` itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use cases ('revoke a staged `url` that was shared by mistake, or one you no longer need') and an explicit when-not-to-use case with the correct alternative ('Files already in a Files surface are not affected (use `delete_file` for those)'). The agent has no routing ambiguity.

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

All Dock toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources