Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

wattpad_user_stories

List a Wattpad author's published stories with metadata such as titles, reads, votes, comments, tags, and completion status; use username, limit, and offset to page through results.

Instructions

List a Wattpad author's stories. Returns one page of the stories a Wattpad author has published, with the same fields as wattpad-search: id, title, description, cover, link, votes, reads, comments, chapter count, completed and mature flags, language, category ids, tags and dates. username is the name from the author's wattpad.com/user/ link. limit is 1 to 100 (default 20) and offset pages the list; next_offset is absent on the last page. Authors with a private profile or who have opted out of crawling are not returned. This call reads the author's access settings first, so it costs two requests.

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, 1 to 100; defaults to 20
offsetNoZero-based result offset; defaults to 0
usernameYesWattpad username from wattpad.com/user/{username}; a profile link or @name is also accepted

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.7/5.0
Behavior5/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 so: it discloses pagination semantics ('next_offset is absent on the last page'), a crawl/auth exclusion ('private profile or opted out of crawling are not returned'), and a cost signal ('costs two requests'). These are non-obvious traits an agent could not get from the schema.

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?

Front-loaded with the purpose, then output shape, then parameter rules, then caveats and cost. Every sentence adds a distinct fact (field list, username format, limit range, pagination end condition, privacy exclusion, request cost) with no repetition of the schema verbatim.

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?

No output schema exists, and the description compensates by enumerating the returned fields (id, title, description, cover, link, votes, reads, comments, chapters, flags, language, categories, tags, dates). Combined with pagination, exclusions, and cost disclosure, an agent has everything needed to call this correctly.

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 schema already documents limit, offset and username. The description still adds value by tying username to the author profile URL and by introducing the next_offset continuation token, which is not in the input schema and tells the agent how to page forward.

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?

Opens with a specific verb+resource: 'List a Wattpad author's stories.' It immediately distinguishes the tool from wattpad_search and wattpad_user by naming the exact resource (an author's published stories) and by cross-referencing that fields match 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 Guidelines4/5

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

Implies the usage scenario (paging through a known author's published catalogue) and gives the key input pattern ('username is the name from the author's wattpad.com/user/ link'). It doesn't explicitly state when to prefer wattpad_user or wattpad_search instead, so the agent must infer the routing, but the context is clear enough.

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