Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

audible_search

Search Audible's audiobook catalog by keyword, title, author, narrator, or category ID. Returns paginated JSON results to find books and audio content.

Instructions

Search Audible's catalog. Searches Audible's audiobook catalog by keyword, title, author, narrator, or category id. At least one filter is required.

Input Schema

NameRequiredDescriptionDefault
qNoFree-text query matched across title, subtitle, and author
pageNoZero-based result page, default 0
limitNoMax results, default 10, max 50
titleNoMatch by title
authorNoMatch by author name
narratorNoMatch by narrator name
category_idNoRestrict to a category id from GET /audible/categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

B3.4/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 disclosure burden. It does surface the real behavioral constraint that at least one filter is required, but says nothing about return shape, pagination behavior, or result caps beyond what the schema implies. Adequate but with clear gaps for an un-annotated tool.

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 and short, with the facet list and the hard constraint placed early. Minor redundancy between 'Search Audible's catalog' and 'Searches Audible's audiobook catalog by...', but nothing that harms comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter search tool with no annotations and no output schema, the description covers the required-filter rule but omits any indication of what a result contains, paging behavior relative to the page/limit params, or how results relate to the category_id source. Enough to call it, not enough to call it confidently.

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% and each parameter is already documented, so the baseline is 3. The description echoes the facet list (keyword, title, author, narrator, category id) but adds no syntax, format, or interaction details beyond the schema.

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 (search) plus the resource (Audible's audiobook catalog) and enumerates the matching facets. Clear what it does, but it does not name or differentiate from siblings like audible_categories / audible_category / audible_charts, leaving the agent to infer when browsing is preferable.

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?

The line 'At least one filter is required' is a usable precondition. However no alternatives are named (e.g., use audible_categories to browse, audible_product for a fixed title), and the required-filters claim is left to inference rather than explicit guidance on choosing among the several sibling search/browse tools.

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