Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_store_product_image

Read-only

Retrieve a single product image from a Mailchimp e-commerce store. Returns the image's URL and associated variant IDs for inspection.

Instructions

Retrieve a single image attached to a product in an e-commerce store.

Use to inspect one image's URL and variant associations. 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. Obtain from list_store_product_images.

Returns: JSON with the image object (id, url, variant_ids).

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": "get_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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description's mention of 'retrieve' and the return format ('JSON with the image object') adds value beyond annotations. No contradictions, and it discloses that the tool inspects one image without side effects.

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 concise: a purpose sentence, a context sentence, an Args section, and a Returns section. No fluff, well-organized, and front-loaded with the main action.

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?

Given the tool has 4 parameters (3 required) and an output schema, the description covers required parameters, return value, and integration context (manual vs synced). It omits the optional account parameter but is otherwise complete for typical use.

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?

Despite 0% schema description coverage, the description explains the three required parameters (store_id, product_id, image_id) with clear instructions on how to obtain them. The optional 'account' parameter is not explained, but it is the only gap.

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 specifies the verb 'retrieve' and resource 'a single image attached to a product', clearly distinguishing it from sibling tools like list_store_product_images and get_store_product. It also mentions inspecting URL and variant associations, making the purpose concrete.

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?

The description states when to use the tool (inspect one image's URL and variant associations) and provides context about manual vs synced stores, implying when automated alternatives exist. It does not explicitly list exclusions but references list_store_product_images to obtain image_id, giving clear guidance.

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