Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wattpad_search

Search Wattpad stories by text, ranking, category, or language and browse paginated results with titles, authors, votes, reads, tags, and completion data.

Instructions

Search and browse Wattpad stories. Searches Wattpad's story catalog by text or browses it by ranking, category and language, and returns one page of stories: id, title, description, cover, link, author, votes, reads, comments, chapter count, completed and mature flags, language, category ids, tags and dates. Give at least one of query, filter, category or language. filter is hot, new or featured; category is an id from wattpad-categories; language is an id from wattpad-languages. limit is 1 to 100 (default 20) and offset pages the results: a text search reaches offset 9999, while browsing without a query is capped at 1500 results. Browse pages can hold fewer stories than limit (or none) because Wattpad filters after paging, so advance with next_offset rather than the item count.

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, 1 to 100; defaults to 20
queryNoText to search for in story titles, descriptions and tags, up to 200 characters
filterNoRanking: hot is currently popular, new is recently published, featured is Wattpad's featured stories
offsetNoZero-based result offset; below 10000 with query, below 1500 without
categoryNoCategory id from wattpad-categories, for example 4 for Romance
languageNoStory language id from wattpad-languages, for example 1 for English

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.3/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 result caps (offset 9999 with a query, 1500 without), and warns that browse pages can return fewer stories than limit or none because Wattpad filters after paging. That last point is exactly the failure mode an agent would otherwise misdiagnose. It omits only the fact that reads are non-mutating, which is self-evident for a search.

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 and constraint, then progressively finer detail, with no filler sentences. The mid-sentence enumeration of returned fields is dense enough to be slightly hard to scan, but nothing is redundant.

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?

No output schema exists, and the description compensates by enumerating the returned story fields and naming next_offset for pagination, so an agent can both interpret and page results. The only gap is that next_offset isn't introduced in the field list where a reader would first look for it.

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 baseline is 3, but the description adds genuine meaning beyond the schema: the interplay of offset caps with the presence of query, the cross-tool pointer for category and language id sources, and the instruction to page with next_offset rather than item count — a value the schema field types do not convey.

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+resource ("search and browse Wattpad stories") and immediately distinguishes the two modes — text search by query vs browsing by ranking/category/language. It also names the sibling lookups (wattpad-categories, wattpad-languages) that supply id values, so an agent knows this is the catalog entry point, not a story detail or user tool.

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?

"Give at least one of query, filter, category or language" is an explicit precondition, and the filter semantics (hot/new/featured) tell the agent which browse mode to pick. It doesn't reference alternatives like wattpad_story_recommendations or wattpad_user_stories, so it falls short of full when/when-not routing.

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