Skip to main content
Glama

ai_modeling_image_delete

Destructive

Delete selected image outputs from your library by specifying asset IDs and keys, so you can remove unwanted generated images and keep your collection organized.

Instructions

Delete selected image outputs from your library.

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": {
      "items": "<items>"
    },
    "name": "ai_modeling_image_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.6/5.0
Behavior2/5

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

The destructiveHint=true annotation already communicates that this is a destructive operation. The description adds only the scope ('from your library') and does not explain irreversibility, permission requirements, or what happens to associated assets or metadata.

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?

The definition is a single short sentence with no unnecessary wording. It is front-loaded with the action and resource, though its conciseness comes at the cost of missing essential detail covered in other dimensions.

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

Completeness2/5

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

Given that this is a destructive batch operation with no output schema and 0% parameter description coverage, the description is far too thin. An agent lacks guidance on parameter construction, safety implications, and expected behavior after invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain the required 'items' array, the 'asset_id' field, or the 'keys' field. It gives no meaning beyond the schema itself, which is a significant gap for a nested batch-delete parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Delete') and resource ('selected image outputs') with a clear scope ('from your library'). It is distinguishable from siblings like ai_modeling_image_get or ai_modeling_image_process, though it does not explicitly name an alternative.

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?

There is no guidance on when to use this tool versus alternatives such as ai_modeling_image_process or other delete tools. The only implied usage is deleting image outputs, but no conditions, exclusions, or prerequisites are stated.

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

Deploy Server

Other Tools