voc-amazon-reviews
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VOC_API_KEY | Yes | Your Shulex VOC API key. Get one free at https://apps.voc.ai/openapi | |
| ANTHROPIC_API_KEY | No | Your Anthropic API key. Only needed for extract_listing_improvements tool. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_reviewsA | Fetch raw Amazon reviews for an ASIN via the Shulex VOC API. No analysis — returns the raw review array plus metadata. Use this when
you want to plug reviews into your own analysis pipeline, or when you
plan to call Args: asin: 10-character Amazon product ID (e.g. "B08N5WRWNW"). market: Market code (US, GB, DE, FR, IT, ES, JP, AU, CA, MX) or amazon.* domain ("amazon.co.uk"). Default: US. limit: Number of reviews to fetch (1-1000). Default: 100. Returns: { "reviews": [{rating, title, body, date, verified, ...}, ...], "meta": {asin, market, total_available, fetched} } |
| analyze_reviewsA | Run AI analysis on reviews you already have. Useful when you fetched reviews via Args:
reviews_json: Either fetch.sh's Returns: {asin, market, report_markdown, sentiment, pain_points, selling_points, tips, summary_zh, summary_en} |
| voc_fullA | One-shot: fetch reviews AND run AI analysis. The default tool for "give me a VOC report on this ASIN" style requests.
Internally equivalent to Args: asin: 10-character ASIN. market: Market code or amazon.* domain (default: US). limit: Number of reviews to fetch (default 100, max 1000). Returns: Same shape as |
| extract_listing_improvementsB | Differentiator tool — derive specific, copyable listing improvements from the VOC report, grounded in actual customer language. Instead of raw search-volume tables (Data Dive style), Claude reads the full VOC report and produces a title, 5 bullets, a description paragraph, and missing keywords — each suggestion citing the pain point it preempts or selling point it amplifies. Requires ANTHROPIC_API_KEY. Costs ~$0.05-0.20 per call (claude-opus-4-7). |
| analyze_csvA | Analyze any review CSV / Excel — not just Amazon. Drag in a Helium 10 export, an eBay / AliExpress scrape, or your own
Shopify export. The loader fuzzy-matches column names ( Use this when:
Args: csv_path: Local path or HTTP(S) URL to a .csv / .xls / .xlsx file. product_name: Optional friendly name for the report header. market: Optional marketplace tag (US / GB / OTHER, etc.). Returns: Same shape as |
| render_dashboardA | Render a VOC report as a standalone black-gold HTML dashboard. The output is single-file HTML — no external dependencies, opens directly
in any browser. Includes sentiment bar, pain-point / selling-point
panels, executive summary, and (if Args:
report: Output from Returns: {html, bytes, output_path} |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Most tools have distinct purposes, but `analyze_reviews` and `voc_full` can be confused since both produce a VOC report, differing only in fetching. `analyze_csv` overlaps conceptually with `analyze_reviews` but is differentiated by input type. Descriptions help clarify but some ambiguity remains.
Names mostly follow verb_noun pattern (analyze_csv, fetch_reviews, render_dashboard) but `extract_listing_improvements` is longer and `voc_full` breaks the pattern entirely. Inconsistent but still readable.
6 tools is well-scoped for the domain of Amazon review analysis. Each tool covers a distinct step (fetch, analyze, improve, render, external CSV analysis) without being too many or too few.
Core workflow (fetch, analyze, improve, visualize) is complete. Minor gaps: no tool for comparing multiple ASINs or batch processing, but this is acceptable for a focused toolkit.