Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wattpad_story

Fetch a Wattpad story's public details—title, author, reads, tags, and chapter count—by numeric story ID or full wattpad.com link. Returns not found if it doesn't exist.

Instructions

Get a Wattpad story. Returns one Wattpad story's public details: title, description, cover, link, author, votes, reads, comments, chapter count, completed and mature flags, language, category ids, tags, first chapter id, last published date, rating and copyright codes, paywall flag and dates. story_id is the numeric id from the story's wattpad.com link; the full link is also accepted. A story that does not exist returns not found. 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.2/5.0
Behavior4/5

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

No annotations exist, so the description carries the burden and does well: it declares the data is public-only, that a missing story returns not found, and that chapter body text is excluded. It omits auth/rate-limit or caching behavior, but for a read-only public lookup those are minor.

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 the core action, then the field inventory, then the input format note and the negative constraint. The field enumeration is long but each item earns its place by telling the agent what it can rely on; slightly denser than it needs to be as a single run-on sentence.

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?

With no output schema and no annotations, the description compensates fully: it enumerates every returned field, defines the identifier format, and states the not-found and no-chapter-text behaviors. An agent has everything needed to call it and interpret the result.

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% and the schema already says a numeric id or a wattpad.com/story link is accepted, so the description largely restates it. It adds the useful clue that the id is extractable from the story's wattpad.com link, but no extra syntax or edge-case handling. 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 a Wattpad story') and then enumerates the returned public fields, so the agent knows exactly what payload this produces. The closing line 'Chapter text is never returned' cleanly separates it from chapter/part-level siblings without naming them.

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?

'Chapter text is never returned' implies the boundary against wattpad_part / wattpad_story_parts, giving clear context for when this tool is the right pick. It stops short of explicitly naming the alternative tool, so routing still requires a small 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