Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

audible_product_related

Find Audible titles related to a given audiobook ASIN by same series, narrator, author, next in series, or raw similarity.

Instructions

Get Audible titles related to an audiobook. Returns Audible titles related to a given ASIN by a required relation type: same series, same narrator, same author, next in series, or raw similarity.

Input Schema

NameRequiredDescriptionDefault
asinYesAudible ASIN
limitNoMax results, default 10, max 50
similarity_typeYesHow to relate titles to the given ASIN

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / similarity_type / enum
      Added value: +[
+  "InTheSameSeries",
+  "ByTheSameNarrator",
+  "RawSimilarities",
+  "ByTheSameAuthor",
+  "NextInSameSeries"
+]
  2. Addedv1.16.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It implies a read-only lookup ('Get', 'Returns') and discloses that similarity_type is mandatory, but says nothing about authentication, ordering, or pagination behavior of the returned list.

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 purpose and then the relation detail. The second sentence slightly restates the first ('Returns Audible titles related to a given ASIN') before adding the new information, a minor redundancy.

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 simple related-titles tool this covers the essentials, but with no output schema and no annotations the description could say more about the shape of results (e.g. whether full title metadata is returned) and ordering before an agent commits. Adequate but with visible gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the enum and limit descriptions already document all three parameters, and the baseline would be 3. The description adds modest value by restating the enum choices in natural language (e.g. 'raw similarity' for RawSimilarities), clarifying intent rather than syntax.

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 and resource ('Get Audible titles related to an audiobook') and enumerates the five relation modes, so the agent knows exactly what class of result to expect. It does not explicitly contrast itself with close siblings like audible_product, audible_series, or audible_search, so it stops short of a 5.

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 description makes clear that a relation type is required and lists the five options, which is useful operational guidance. However, it never says when to prefer this tool over alternatives such as audible_series (series listing) or audible_search, leaving the choice 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