Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

audible_editorial_list

Fetch Audible's hand-curated Popular Lists by slug (audiobooks, booktok, podcasts) to get themed shelves with headings and ordered ASINs for product detail lookups.

Instructions

Get an Audible curated editorial list. Returns one of Audible's hand-curated "Popular Lists" pages, as its themed shelves (heading + ordered ASINs). Pair an ASIN from any shelf with GET /audible/products (batch) or GET /audible/product/{asin} for full title/author/price/rating detail. "Best of the Year" is not covered.

Input Schema

NameRequiredDescriptionDefault
listYesEditorial list slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / list / enum
      Added value: +[
+  "audiobooks",
+  "booktok",
+  "podcasts"
+]
  2. Addedv1.16.0

TDQS

A4.3/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 burden and does disclose meaningful behavior: the return is themed shelves (heading + ordered ASINs) and one editorial list is out of scope. It omits pagination, auth, and rate-limit behavior, but the return-shape and coverage-gap disclosure is genuinely useful context.

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 sentences, front-loaded with identity, then return shape, then follow-up routing and the coverage caveat. No filler; each sentence earns its place.

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

Completeness5/5

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

For a one-parameter enum getter with no output schema and no annotations, the description compensates by describing the return structure, how to expand ASINs into detail, and what is not covered. An agent has everything needed to call it correctly.

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?

The single `list` parameter has 100% schema description coverage with an enum, so the schema already documents it. The description adds the notion of "Popular Lists" pages but does not explain what the enum values audiobooks/booktok/podcasts mean, so baseline 3 is appropriate.

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 an Audible curated editorial list") and pins down the return shape (hand-curated "Popular Lists" rendered as themed shelves of heading + ordered ASINs). This lets an agent separate it from the algorithmic sibling audible_charts / audible_categories without opening the 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?

Gives clear downstream guidance — pair a returned ASIN with GET /audible/products (batch) or GET /audible/product/{asin} — and flags a concrete exclusion ("Best of the Year" is not covered). It does not explicitly say when to prefer this over audible_charts or audible_categories, so it stops short of full alternative routing.

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