Skip to main content
Glama

Delete Asset

sirv_delete_asset
DestructiveIdempotent

Moves a single library asset to the trash for soft deletion, allowing later restoration. Use it for one asset at a time, not bulk operations or CDN files.

Instructions

Move one library asset to the trash (soft delete). It can be restored: in Studio, or with sirv_bulk_edit_assets and the restore operation.

Use it for one asset. Do not use it for many assets (use sirv_bulk_edit_assets) or for a file in the connected Sirv account (use sirv_cdn_manage_file).

Input: id, the asset id from sirv_list_assets.

Returns the asset id.

Credits: free.

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": {
      "id": "<id>"
    },
    "name": "sirv_delete_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the asset to move to the trash, from sirv_list_assets
orgIdNoWorkspace id from sirv_list_organizations. Default: the workspace you signed in to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • changedInput schema / properties / id / description
      Previous value: -"Asset ID to soft-delete"New value: +"Id of the asset to move to the trash, from sirv_list_assets"
    • changedInput schema / properties / orgId / description
      Previous value: -"Organization ID (uses default org if omitted)"New value: +"Workspace id from sirv_list_organizations. Default: the workspace you signed in to"
    • addedInput schema / properties / orgId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. First observedv0.1.0

TDQS

A4.7/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, but the description adds the critical nuance that this is a recoverable soft delete and spells out both restore paths (Studio, or sirv_bulk_edit_assets with the restore operation). It also discloses the return value ('Returns the asset id') and that the call is credit-free, none of which is in the structured data. This resolves the apparent tension between 'destructive' and 'restorable' rather than contradicting it.

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?

Front-loads the action and its soft-delete nature, then alternatives, then input/output, then cost — a logical order for an agent scanning it. Every sentence is load-bearing; there is no repetition or filler.

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?

Although there is no output schema, the description states the return value and the input source, and it covers reversibility, sibling routing, and cost. For a two-parameter delete tool this leaves no meaningful gap an agent would need to fill before calling it.

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%, so both `id` and `orgId` are already documented in the schema. The description restates `id` and its provenance (sirv_list_assets) but adds nothing on the optional `orgId` workspace scoping. Baseline 3 applies when the schema carries the parameter burden.

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 and resource ('Move one library asset to the trash') and immediately qualifies scope with 'soft delete'. It further pins down the unit of operation ('one asset') so the agent can distinguish it from bulk and CDN-file operations without opening 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 Guidelines5/5

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

Gives explicit positive guidance ('Use it for one asset'), explicit exclusions ('Do not use it for many assets', 'or for a file in the connected Sirv account'), and names the correct alternative sibling for each case (sirv_bulk_edit_assets, sirv_cdn_manage_file). Nothing is left to inference.

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