Amazon Creators API MCP Server — blog-friendly affiliate product embeds rendered inline via MCP Apps.
Server has 5 well-named tools with clear verb-noun patterns (search_items, get_items, get_variations, get_browse_nodes, format_items). All tools have descriptions (avg ~80 chars, within baseline 34-392 range). Input schemas are present and typed with enums for format parameters. However, parameter descriptions are sparse or missing for several fields (e.g., customStyles lacks guidance on CSS format; titleMaxChars has no range constraints). Output schemas are not documented, LLMs cannot predict response structure for chaining. Error handling is minimal; no recovery guidance or categorization. Security is adequate (no secrets in params, read-only operations), but composition could be tighter, format_items duplicates formatting logic across tools rather than centralizing it.
Re-render previously fetched Amazon product data in different formats without hitting the API
Get browse node information for Amazon product categories
Get detailed information about Amazon products by ASIN
Get product variations for a parent ASIN
Search for Amazon products by keywords
Output schemas not documented. LLMs cannot predict response structure (fields, types, nesting) for downstream tool chaining or data extraction. Smoke tests show responses exist but no schema is published in tool definitions.
Parameter descriptions incomplete or missing guidance. 'customStyles' (present in 4 tools) lacks format/constraint info; 'titleMaxChars' has no min/max bounds; 'variationCount' and 'itemCount' lack range constraints.
Error handling lacks recovery guidance. Smoke tests catch errors but do not guide LLM on retry strategy, user-fixable vs fatal classification, or next steps. Per pattern:recovery-guide, errors must tell the agent what to do.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 53 | 2025-06-18+ | v2 |
format_items duplicates formatting logic already present in search_items and get_items. Per pattern:tool, each tool should do exactly one thing. Consider consolidating format handling or making it a utility rather than a user-facing tool.
No pagination support documented. Tools accept itemCount/variationCount but no limit enforcement, offset/cursor, or total count in responses. Per pattern:paginated-result, large result sets must support pagination to avoid context window exhaustion.