Skip to main content
Glama
damientilman

Mailchimp MCP

create_store_product_image

Attach an image to an e-commerce product by providing a unique image ID and a publicly reachable URL. Specify the store and product to associate the image.

Instructions

Add an image to a product in an e-commerce store.

image_id is client-supplied and must be unique within the product; url must point to a publicly reachable image. Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync product images automatically.

Authenticated via API key. Max 10 concurrent requests. Respects read-only and dry-run modes.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. product_id: Product ID to attach the image to. image_id: Client-supplied unique ID for the new image (e.g. 'img_1'). url: Publicly reachable URL of the image. additional_fields: Optional dict of extra image fields merged into the body (e.g. variant_ids). account: Optional account name (e.g. 'marketing') configured via MAILCHIMP_API_KEY_. Omit to use the default account. See list_accounts.

Returns: JSON with the created image object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
accountNo
image_idYes
store_idYes
product_idYes
additional_fieldsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Beyond annotations, discloses authentication via API key, max 10 concurrent requests, and respect for read-only/dry-run modes. No contradictions with annotations.

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?

Well-structured with a clear opening, contextual details, enumerated Args, and a return statement. No unnecessary information.

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?

Covers purpose, all parameters, usage context, authentication, limits, and output. References related tools for obtaining IDs. Comprehensive for a tool with 6 parameters and no schema descriptions.

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

Parameters5/5

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

With 0% schema coverage, the description compensates fully by explaining all 6 parameters, including examples and cross-references to other tools (e.g., list_ecommerce_stores).

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 'Add an image to a product in an e-commerce store.' It distinguishes this tool from siblings by specifying it is for manual stores, while Shopify and WooCommerce sync automatically.

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?

Provides context on when to use (manual stores) and preconditions (image_id uniqueness, public URL). Does not explicitly list alternatives but implies comparison with integrations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/damientilman/mailchimp-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server