Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

audible_products

Fetch details for up to 50 Audible audiobooks in one request by ASIN, returning the same fields as a single-product lookup while skipping unrecognized ASINs.

Instructions

Get multiple Audible audiobooks in one call. Returns Audible audiobooks for up to 50 ASINs in a single request — the same fields as GET /audible/product/{asin}. Unrecognized ASINs are silently omitted rather than failing the whole batch.

Input Schema

NameRequiredDescriptionDefault
asinsYesComma-separated Audible ASINs, up to 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does add real value: the 50-ASIN cap, the partial-success semantics ('unrecognized ASINs are silently omitted rather than failing the whole batch'), and the shared return shape. It omits auth requirements and rate limits, but the error-handling disclosure is the important behavioral trait an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three tight sentences, front-loaded with the core action, then scope, then edge-case behavior. Every sentence earns its place with no redundancy.

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 single-parameter read tool, the description covers scope, return shape and partial-failure handling. Its one soft spot is defining the return value by reference to GET /audible/product/{asin} rather than describing fields, though the batch-limit and omission behavior is well covered.

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 the schema already documents the 'asins' parameter, its comma-separated format and its 50-item limit. The description restates the limit but adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('Get multiple Audible audiobooks in one call') and makes the batch scope explicit ('up to 50 ASINs in a single request'). This distinguishes it from the single-item audible_product sibling without the agent having to open either schema.

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

Usage Guidelines4/5

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

The batch framing ('multiple ... in one call', 'up to 50 ASINs') clearly implies when to choose this over the single-ASIN sibling. However, it never explicitly names the alternative or states an exclusion condition, so it stops short of a 5.

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