list_media_imagesRetrieve all images from a shop's media library. Use this to list available media assets for products or content.
Rate limit: 100 requests / 10 seconds per shop. See Rate limiting.
Retrieves all images from the shop's media library
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | Exact private shop profile label; not a provider identity or authorization proof. |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds a genuine behavioral detail beyond the structured data: the rate limit (100 requests / 10 seconds per shop), with a link to further documentation.
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?
Two short sentences with no filler. The rate-limit line is arguably front-loaded ahead of the actual purpose statement, which slightly delays the core description, but overall it is tight and efficient.
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?
With one fully documented parameter (account) that is not required, no output schema, and annotations covering the safety profile, the definition supplies enough context to call the tool correctly. Return format and pagination behavior are unaddressed, a minor gap for a list endpoint with no output schema.
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 100% and the single 'account' parameter is fully documented in the schema, so baseline is 3. The description adds no parameter-level meaning beyond what the schema provides.
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 states a specific verb ('Retrieves') and resource ('all images from the shop's media library'), which is clear. It does not explicitly differentiate itself from sibling media tools like save_media_image or remove_product_images, but the read-only listing purpose is unambiguous.
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?
There is no guidance on when to use this tool versus alternatives such as list_products, list_collections, or the other media-library tools (save_media_image, request_media_upload_url). Usage must be inferred entirely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.