WhizzyCommerce

products_remove_image

Take a picture off a product. Money is integer minor units (cents). Calling this changes nothing: it returns a preview of what would change and a confirmation link. Only the merchant, on that page, can make it happen.

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": {
      "product": "<product>",
      "picture": "<picture>"
    },
    "name": "products_remove_image"
  }
}

Input Schema

Name	Required	Description	Default
`picture`	Yes	Which picture, 1 being the first (list_products says how many there are).
`product`	Yes	The product, by handle or by (enough of) its title.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior3/5

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

It adds real behavioral context beyond the annotations: no immediate mutation, a preview is returned, a confirmation link is issued, and only the merchant can complete it. However, 'Calling this changes nothing' sits in mild tension with readOnlyHint=false, and the description does not reconcile that the tool is the entry point to a destructive workflow. The stray sentence about money in minor units describes no parameter on this tool and adds noise rather than transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first clause, followed by the confirmation semantics, which is the right order. The money sentence is dead weight carried over from another tool and slightly dilutes an otherwise tight, four-sentence definition.

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?

With no output schema, the description correctly carries the burden of describing the return value (a preview of what would change plus a confirmation link) and the merchant-only completion step. That covers what an agent needs to call it and interpret the result. It stops short of describing what the preview contains or what happens after confirmation.

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?

Schema coverage is 100%, so the schema already defines both parameters, including that 'picture' is a 1-based index cross-referenced by list_products. The description adds no parameter meaning of its own, and the 'Money is integer minor units (cents)' sentence is irrelevant to a tool with no monetary parameter, so baseline 3 is appropriate.

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 first sentence states a specific verb and resource ('Take a picture off a product'), which is unambiguously the inverse of the sibling products_add_image and clearly distinct from products_add_download or products_edit. An agent can identify the operation without opening the schema.

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 explains the operating model clearly: invoking the tool does not perform the removal, it returns a preview plus a confirmation link that only the merchant can act on. That is strong when/how guidance for a confirmation-gated workflow. It does not name an alternative tool or state when removal should be avoided, which keeps it short of a 5.

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

All WhizzyCommerce tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.