Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

audible_product_related

Find related Audible titles by ASIN and relation type: same series, narrator, author, next in series, or raw similarity. Returns credential-free public catalog data.

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 upstream similarity. Credential-free public catalog data from api.audible.com.

Input Schema

TableJSON 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

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description takes on the transparency burden and handles it well: it states the tool is credential-free, reads public catalog data, and pulls from api.audible.com. The word 'Get' and 'public catalog data' imply a read-only, non-destructive operation. It does not cover response pagination or error behavior, but for a simple public lookup it discloses the key operational traits.

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 short sentences with zero filler. The core action and relation types are front-loaded, and the credential/source note is a single relevant closing sentence. Every sentence carries information an agent needs.

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?

The tool is simple, the schema fully documents parameters, and the description supplies purpose, relation semantics, and credential requirements. No output schema exists, but the description states that the result is related Audible titles, which is enough for an agent to invoke and interpret the call. A slightly more explicit return-structure note would be the only enhancement.

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 baseline is met. The description adds value by translating the enum values into plain language, especially clarifying 'RawSimilarities' as 'raw upstream similarity' and distinguishing 'same series' from 'next in series.' That goes beyond the bare schema without being verbose.

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?

The description opens with a specific verb and resource: 'Get Audible titles related to an audiobook.' It then enumerates the relationship modes (same series, same narrator, same author, next in series, raw upstream similarity), leaving no ambiguity about the operation. This clearly distinguishes it from product-detail or search tools among the Audible siblings.

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 description gives clear context: use this tool when you need Audible titles related to a specific ASIN under one of five named relation types. It also signals that no credentials are required, which is useful routing information. It does not explicitly name sibling alternatives or state when not to use it, 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