Skip to main content
Glama

Delete an image

delete_image
DestructiveIdempotent

Remove one image so the chatbot stops showing it. Needs the Standard plan or higher.

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": {
      "image_id": "<image_id>"
    },
    "name": "delete_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_idYesImage id from list_images.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered; the description still adds real context by stating the observable consequence (the image stops being shown by the chatbot) and the plan-level authorization requirement. It does not state whether deletion is permanent or recoverable, which is the remaining behavioral gap.

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 short sentences with the action and its effect front-loaded, followed by the plan constraint. Nothing is redundant and nothing crowds out the essential information.

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 single-parameter destructive delete with full annotation coverage and no output schema, the description covers purpose, effect, and authorization tier adequately. The only missing piece an agent might want is confirmation of irreversibility or post-delete behavior, which is a minor gap.

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?

There is exactly one parameter and the schema documents it at 100% coverage, including the hint to obtain it from list_images. The description adds no additional meaning about the parameter (no format, scope, or validation notes), so the baseline 3 applies.

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?

States a specific verb and resource ("Remove one image") plus the user-visible effect ("so the chatbot stops showing it"), which separates it from add_image and list_images. It does not explicitly name the sibling that lists images, relying instead on the schema's "Image id from list_images" note for that routing.

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

Usage Guidelines3/5

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

"Needs the Standard plan or higher" is a genuine prerequisite that helps an agent decide whether the call can succeed at all. However, there is no explicit when-to-use vs when-not guidance (e.g., prefer hiding/removing from a set versus deleting) and no mention of what to do if the id is wrong, leaving the alternative selection implied.

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