Crawlora MCP

wattpad_user_stories

Read-only

List the stories a Wattpad author has published and return each story's id, title, description, votes, reads, comments, chapter count, completed flag, language, category ids and tags. Use this to see an author's full catalog and which works perform best after finding them with wattpad_user; page with next_offset, and authors with a private profile or who opted out of crawling are not returned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "username": "<username>"
    },
    "name": "wattpad_user_stories"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Page size, 1 to 100; defaults to 20
`offset`	No	Zero-based result offset; defaults to 0
`username`	Yes	Wattpad username from wattpad.com/user/{username}; a profile link or @name is also accepted

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds two things annotations cannot: pagination via next_offset and a data-availability caveat that private profiles and opted-out authors are excluded. That exclusion is the kind of context that prevents wasted calls; only the return-shape enumeration is redundant against the output schema.

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 usage and pagination caveat. The long field enumeration (id, title, description, votes, reads, comments, chapter count...) is redundant with the output schema and would be the first thing to cut.

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 read-only paginated listing with a full output schema and 100%-covered input schema, the description covers purpose, sequencing, pagination and the exclusion rule. Nothing an agent needs to call it correctly is missing, aside from a clearer statement of what next_offset is.

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 limit, offset and username are already documented. The description adds only a pagination hint ('page with next_offset'), and that phrasing could be misread against the actual 'offset' input parameter, so it compensates for nothing and adds mild ambiguity.

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 plus resource ('List the stories a Wattpad author has published') and scopes it to one author. This clearly separates it from wattpad_user (author lookup) and wattpad_story (single story detail) among the wattpad_* siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly sequences the tool: find the author with wattpad_user, then call this to see the full catalog and rank works by popularity. That is a concrete when-to-use and which-alternative-first instruction, not an implication.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?