Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wattpad_story_parts

Lists a Wattpad story's chapters in reading order with word counts, reads, votes, and comments, so you can see how it is paced and where readers drop off.

Instructions

List a Wattpad story's chapters. Returns a Wattpad story's chapter list, in reading order: id, title, link, word count, reads, votes, comments, length, and created and modified dates for every chapter. The per-chapter reads show where readers drop off. Use it to see how a story is paced and which chapters readers react to. story_id is the numeric story id, or its wattpad.com link. Chapter text is never returned.

Input Schema

NameRequiredDescriptionDefault
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

A4/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and does so well: it declares ordering ("in reading order"), enumerates every returned field, and states a negative boundary ("Chapter text is never returned"). It omits pagination/limit behavior for long stories, which matters for a listing call.

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 verb+resource, then returns, then interpretation. "The per-chapter reads show where readers drop off" and "which chapters readers react to" are slightly redundant but each sentence is short and purposeful.

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 single-parameter, annotation-free, no-output-schema tool, the description supplies what the structured fields cannot: the exact return shape, the ordering guarantee, a negative boundary, and the analytical use case. Nothing an agent needs to call it correctly appears 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?

The single parameter is 100% documented in the schema, and the description's "numeric story id, or its wattpad.com link" largely restates that. Baseline 3 applies since the schema already does the work and the description adds no new format or validation guidance.

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?

"List a Wattpad story's chapters" gives a specific verb and resource, and the returned-field enumeration makes the scope precise. It does not name the sibling (wattpad_part) that produces the chapter text it explicitly withholds, so the sibling differentiation is implied rather than stated.

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?

"Use it to see how a story is paced and which chapters readers react to" gives a clear analytical context for selecting this tool. It lacks an explicit exclusion (e.g. "use wattpad_part to read chapter text"), so the alternative path is only hinted at via "Chapter text is never returned."

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