Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

audible_product_reviews

Fetch customer reviews for an Audible audiobook by ASIN, including ratings, review text, helpful votes, and dates. Use page and limit to retrieve structured review data.

Instructions

Get an Audible audiobook's customer reviews. Returns a page of an Audible audiobook's customer reviews (author, title, body, overall/performance/story ratings, helpful votes, submission date).

Input Schema

NameRequiredDescriptionDefault
asinYesAudible ASIN
pageNoZero-based result page, default 0
limitNoMax reviews, default 10, max 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It helpfully enumerates the fields returned (ratings, helpful votes, submission date), which compensates for the absent output schema. However, it discloses nothing about pagination semantics, permissions, or rate limits beyond the bare 'page' wording.

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?

Two sentences, front-loaded with the core action. Minor redundancy in repeating 'customer reviews' between sentence one and the parenthetical list, but nothing wasteful.

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 read-only review-list tool with no annotations and no output schema, the description adequately covers both the input (via schema) and the notable return fields. It is complete enough for an agent to call correctly, with only pagination behavior left implicit.

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 description coverage is 100%, so asin, page, and limit are already fully documented with defaults and ranges. The description adds no parameter meaning beyond that, making the baseline 3 appropriate.

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?

Clear specific verb+resource: 'Get an Audible audiobook's customer reviews'. An agent immediately knows what it retrieves. It does not differentiate itself from siblings like audible_product or audible_products, but the 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.

Usage Guidelines2/5

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

No when-to-use guidance at all — nothing about when to prefer this over audible_product or other review sources. The description states only what it does, leaving the agent to infer the invocation context.

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

Deploy Server

Other Tools