Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

delete_store_product_image

DestructiveIdempotent

Permanently delete a product image from your e-commerce store. Removes the image and cannot be undone, ideal for managing product visuals.

Instructions

Permanently delete an image from a product in an e-commerce store.

This removes the image and cannot be undone. Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync product images automatically.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. product_id: Product ID that owns the image. image_id: Image ID to delete.

Returns: JSON confirming deletion (empty body on success) or an error object.

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": {
      "store_id": "<store_id>",
      "product_id": "<product_id>",
      "image_id": "<image_id>"
    },
    "name": "delete_store_product_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
image_idYes
store_idYes
product_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4.5/5.0
Behavior4/5

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

The description adds significant behavioral context beyond annotations: it explicitly states the permanent, irreversible deletion and the return format (empty body on success or error object). Annotations already mark destructiveHint=true and idempotentHint=true, so the description reinforces and supplements these.

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?

The description is extremely concise: two short paragraphs front-load the action and separate purpose from arguments/returns. Every sentence adds value with no filler or redundancy.

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?

For a simple delete operation with four parameters, the description covers all necessary aspects: action, permanence, use-case distinction, parameter meanings, source hints, and return behavior. No gaps remain for the agent to invoke the tool correctly.

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

Parameters4/5

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

With 0% schema description coverage, the description provides meaningful guidance for all three required parameters (store_id, product_id, image_id), including the source for store_id. The optional 'account' parameter is not described, but the core parameters are well-covered.

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 clearly states the specific verb-resource pair ('Permanently delete an image from a product') and distinguishes this tool from integrated platform sync (Shopify/WooCommerce), differentiating it from sibling tools like update_store_product_image or other delete operations.

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

Usage Guidelines4/5

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

It provides explicit usage context: manual/custom stores vs integrated platforms where sync handles images. It also mentions a prerequisite (obtain store_id from list_ecommerce_stores). However, it could more explicitly state when not to use this tool (e.g., for integrated stores), though it's strongly implied.

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