Skip to main content
Glama
houtini-ai

Amazon Creators MCP

by houtini-ai

get_items

Read-only

Look up 1–10 Amazon ASINs to get product data: price, ratings, offers, and images. Output as JSON, markdown, or embeddable HTML cards for your content.

Instructions

Look up 1–10 ASINs on Amazon. IMPORTANT: the returned items array is NOT guaranteed to be in the same order as the input asins array — always match items to inputs by the asin field, not by index. Invalid or inaccessible ASINs appear in a separate errors array rather than in items — check both.

PRESENTATION GUIDANCE (important): default to format: 'markdown' or format: 'json'. After the tool returns, summarise conversationally (e.g. "Here's what I found for those 3 ASINs: • Echo Show 5 ($79.99) • Kindle Paperwhite ($139.99) …") — DO NOT paste the raw tool output. Then ASK the user whether they'd like an embeddable HTML card/grid before calling the tool again with an HTML format. Only use format: 'html-card' or format: 'html-grid' when the user has explicitly asked for a preview, card, widget, embed, or paste-ready HTML.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asinsYes1–10 Amazon ASINs.
formatNoOutput format. DEFAULT TO 'markdown' OR 'json' when you plan to summarise the results in chat. Use 'html-card' / 'html-grid' ONLY when the user has explicitly asked for an embed, preview, card, widget, grid, or paste-ready HTML — these formats return a full HTML document the user pastes into their blog and are not for in-chat reading. 'markdown' = friendly summary source; 'json' = raw API data for programmatic use; 'html-card' = single product card; 'html-grid' = responsive grid of all items.markdown
merchantNo
conditionNo
resourcesNoWhich fields Amazon should return. Names are camelCase (e.g. "itemInfo.title"). Omit to use a sensible default set.
offerCountNoHow many offers per item (max 10).
customStylesNoExtra CSS appended to the default stylesheet when format is 'html-card' or 'html-grid'. Target stable class-name anchors: .amzn-card, .amzn-card__image, .amzn-card__title, .amzn-card__meta, .amzn-card__brand, .amzn-card__rating, .amzn-card__price, .amzn-card__price--unavailable, .amzn-card__savings, .amzn-card__cta, .amzn-card__disclosure, .amzn-grid. Ignored for 'markdown' and 'json'.
titleMaxCharsNoMaximum rendered title length for HTML card/grid output. Amazon titles are often 150+ chars of keyword stuffing; clamping to ~80 keeps cards one-line on typical widths. Defaults to 80. Set to 0 to disable. Ignored by 'markdown' and 'json' — those formats get the full untruncated title.
hideItemsWithoutPriceNoWhen format is 'html-grid', drop items that have no price. Defaults to true — cards without a price are weak embeds (no deal hook, reader must click through to learn anything). Set false for comparison tables where availability can lapse but you still want the product visible. Ignored for 'html-card', 'markdown', and 'json'.
languagesOfPreferenceNo
Behavior5/5

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

Annotations declare readOnlyHint and openWorldHint, and the description adds high-value behavioral details: the returned items array is not ordered, invalid ASINs appear in an errors array, format defaults are specified, and HTML-only styling parameters are explained. No contradiction 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.

Conciseness4/5

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

The description is well-structured with a clear first sentence, bolded warnings, and a separate presentation guidance section. It is longer than necessary with some repetition of format guidance, but the key information is front-loaded and scannable.

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?

For a tool with 10 parameters and no output schema, the description covers critical runtime behavior: array ordering, error handling, output formats, and post-tool presentation. It does not detail merchant/condition/resources, but the schema provides those descriptions. Overall, it is sufficient for correct invocation and result handling.

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?

Schema coverage is 70%, and the description enriches several parameters: it explains format defaulting and HTML usage, titleMaxChars clamping behavior, hideItemsWithoutPrice default, and the asins ordering caveat. This goes beyond the schema's descriptions for those parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Look up 1–10 ASINs on Amazon', which clearly states the specific verb and resource. However, it does not explicitly differentiate from sibling tools like search_items or get_variations, though the focus on ASINs is implied.

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

Usage Guidelines3/5

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

Extensive guidance is provided for choosing output formats (markdown/json vs html-card/html-grid) and for post-tool conversational summarization. However, there is no explicit guidance on when to use get_items versus sibling tools like search_items or get_variations; usage is only implied by the phrase 'Look up ... ASINs'.

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/houtini-ai/amazon-creators-mcp'

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