Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

wattpad_search

Read-only

Search or browse Wattpad stories and return each story's id, title, description, author, votes, reads, comments, chapter count, completed flag, language, category ids and tags. Use this to find popular or new fiction by keyword, ranking (hot, new, featured), category id or language id; give at least one of those, page with next_offset, and note browse pages can be short or empty.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wattpad_search"
  }
}

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. Documented values: hot, new, featured.
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. Documented values: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 46, 47, 48, 49, 50, 51, 53.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, openWorldHint), so the description earns credit for operational detail instead: browse results 'can be short or empty' and paging goes through next_offset. These are non-obvious traits an agent would otherwise discover only by failing. It stops short of saying whether query and filter can be combined or what the offset caps mean in practice.

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?

Two sentences, front-loaded with purpose then usage then the pagination caveat. The long enumeration of return fields (id, title, votes, reads, comments, chapter count, ...) is largely redundant with the output schema and is the one block that does not fully earn its space.

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?

With an output schema present, the description need not explain return shapes, and it covers the two gaps that matter for a search tool: the at-least-one-input rule and unreliable browse page sizes. Missing only edge behavior such as how query interacts with filter/category, which is minor for a read-only open-world search.

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; the description rises above it by stating the minimum-viable parameter combination ('at least one of keyword, ranking, category id, language id'), which the all-optional schema does not convey. Slight ambiguity in referencing 'next_offset' while the input parameter is named 'offset', but that appears to be the pagination handle returned.

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?

The description opens with a specific verb+resource ('Search or browse Wattpad stories') and enumerates the returned fields, making it unmistakably the story-search tool rather than the sibling wattpad_search_users or wattpad_story. An agent can pick it without opening the schema.

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?

It states the four ways to drive a search (keyword, ranking, category id, language id) and imposes a real constraint — 'give at least one of those' — that is not expressed anywhere in the schema, since all six params are optional. It does not name an alternative tool or say when not to use it, so it falls short of a 5.

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

All Crawlora MCP toolsInspect
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