etsy_listing_image_delete
Remove an image from an Etsy listing by providing shop, listing, and image IDs.
Instructions
Delete an image from a listing
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| shop_id | Yes | ||
| listing_id | Yes | ||
| listing_image_id | Yes |
Remove an image from an Etsy listing by providing shop, listing, and image IDs.
Delete an image from a listing
| Name | Required | Description | Default |
|---|---|---|---|
| shop_id | Yes | ||
| listing_id | Yes | ||
| listing_image_id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotation destructiveHint: true already signals the tool is destructive. The description adds no further behavioral context (e.g., permanence, side effects). Credit is given for annotations covering safety, but the description could elaborate on irreversible consequences.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The single-sentence description is concise and to the point. It could be slightly restructured to front-load key constraints, but as a minimal statement it earns a high score for brevity without waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple delete tool with destructiveHint annotation and no output schema, the description is minimally adequate. It lacks details like return type (e.g., 204 No Content) or whether the operation is reversible, but these are less critical given the tool's simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, meaning the description carries full burden to explain parameters. However, the description does not address shop_id, listing_id, or listing_image_id at all. While parameter names are self-explanatory, the description should confirm roles (e.g., 'specify the shop, listing, and image IDs').
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Delete an image from a listing' clearly states the action and resource. However, it does not differentiate from sibling tools like etsy_listing_delete (deleting the entire listing) or etsy_listing_image_update_alt (updating alt text), missing a chance to aid selection.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives, nor are any prerequisites or exclusions mentioned. The description lacks context like 'Use this to remove a specific image; for reordering, use etsy_listing_images_reorder instead.'
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BusyBee3333/etsy-mcp-2026-complete'
If you have feedback or need assistance with the MCP directory API, please join our Discord server