Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

audible_product

Fetch an Audible audiobook by ASIN to retrieve its description, authors, narrators, series, categories, publisher, release date, runtime, language, sample audio URL, ratings, and list price.

Instructions

Get an Audible audiobook. Returns an Audible audiobook: description, authors, narrators, series, category ladders, publisher, release date, runtime, language, sample audio URL, rating (overall/performance/story), and public list price.

Input Schema

NameRequiredDescriptionDefault
asinYesAudible ASIN

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. 'Get' plus the field enumeration makes clear this is a read-only lookup and reveals the return shape, which is genuinely useful. However, it says nothing about auth requirements, error behavior for an invalid/missing ASIN, or rate limits.

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?

Front-loaded with the purpose in one short sentence, followed by a compact field list. Slight redundancy between 'Get an Audible audiobook' and 'Returns an Audible audiobook', but no wasted padding.

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?

With no output schema, the description usefully enumerates what comes back (authors, narrators, ratings, price, sample URL, etc.), which an agent needs to judge relevance. For a single-parameter read tool this is close to complete, missing only failure/auth notes.

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?

Single parameter 'asin' at 100% schema coverage, so the schema already documents the input. The description adds no syntax, format, or lookup guidance for the ASIN beyond what the schema provides; baseline 3 applies.

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?

States a specific verb+resource ('Get an Audible audiobook') and the singular framing distinguishes it from list-style siblings like audible_products and audible_search. It does not explicitly name those siblings, so it falls short of the 5 bar for sibling differentiation, 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 Guidelines3/5

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

Usage is only implied: you fetch a known audiobook by its ASIN. There is no explicit when-to-use/when-not, no mention of the alternative list/search tools, and no prerequisites. Adequate but leaves routing to inference.

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