Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wattpad_story_recommendations

Find stories Wattpad recommends alongside a given story ID or link, returning titles, authors, stats, and tags so you can discover similar reads.

Instructions

List stories Wattpad recommends for a story. Returns the stories Wattpad recommends alongside one story (readers of this also read these), with the same fields as wattpad-search: id, title, description, cover, link, author, votes, reads, comments, chapter count, completed and mature flags, language, category ids, tags and dates. story_id is the numeric story id or its wattpad.com link. Wattpad returns at most 18 recommendations and does not page; limit is 1 to 20.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum recommendations to return, 1 to 20; defaults to 20
story_idYesNumeric Wattpad story id, such as 344352588; a wattpad.com/story link is also accepted

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.9/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 well: it discloses the returned field set, the hard cap of 18, that there is no paging, and the limit range. It omits auth/rate-limit behavior, but the behavioral profile of this read tool is largely conveyed.

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 with purpose, then return fields, then parameter notes. The enumerated field list is somewhat long but earns its place as the only return-value documentation since there is no output schema.

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 simple two-parameter read tool with no output schema, the description supplies what an agent needs: purpose, return shape, the 18-item cap, and no-paging behavior. Nothing critical is missing.

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 coverage is 100%, so both parameters are already documented. The description restates story_id's accepted formats and the limit range; the only marginal addition is noting the effective cap of 18 versus the limit max of 20.

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 ('List stories Wattpad recommends for a story') and clarifies the relationship ('readers of this also read these'). It is clearly distinguishable from sibling tools like wattpad_story and wattpad_search.

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 conveys the concept ('readers of this also read these') which implies when it's useful, but it never explicitly names the alternative tools (wattpad_story, wattpad_search) or states when NOT to use it. Usage is implied rather than directed.

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