Skip to main content
Glama

assets_delete_many

DestructiveIdempotent

Delete multiple VOD assets at once.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "assets_delete_many"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_idNoDeprecated. Use `workspace_id` instead. Still accepted for backwards compatibility.
asset_listNoLIst of asset ids to delete
workspace_idNoGumlet video workspace ID. Preferred over deprecated `collection_id` / `source_id` (same ID).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / source_id / description
      Previous value: -"Workspace ID from which assets needs to be deleted."New value: +"Deprecated. Use `workspace_id` instead. Still accepted for backwards compatibility."
    • addedInput schema / properties / workspace_id
      Added value: +{
      +  "description": "Gumlet video workspace ID. Preferred over deprecated `collection_id` / `source_id` (same ID).",
      +  "examples": [
      +    "646df1c9173a4a2fcac180b4"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds only that the operation targets VOD assets in batch; it does not add permissions, recoverability, or side-effect details beyond the annotations.

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?

It is a single front-loaded sentence with no redundant wording. The core action and scope are immediately clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity batch delete with full schema coverage, an output schema, and annotations covering destructive/idempotent behavior, the description is sufficient. It is sparse but not missing anything required to invoke the tool correctly.

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 all three parameters are already documented in the schema. The description adds no parameter-level meaning beyond implying that asset_list contains multiple asset IDs.

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 states a specific verb ("Delete"), resource ("VOD assets"), and batch scope ("multiple ... at once"), which clearly distinguishes it from the singular delete_asset sibling.

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?

It gives no explicit when-to-use guidance, no comparison to delete_asset or delete_source, and no prerequisites or warnings. The batch use case is only implied by "multiple ... at once."

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