Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wattpad_search_users

Search Wattpad authors by username or name and return one page of profile data, including bio, avatar, verification, story and follower counts.

Instructions

Search Wattpad authors by name. Searches Wattpad's authors by username or name and returns one page: username, display name, bio, avatar, verified flag, published story count and follower count. limit is 1 to 100 (default 20) and offset pages the results. Authors with a private profile or who have opted out of crawling are left out, so a page can hold fewer authors than limit; advance with next_offset.

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, 1 to 100; defaults to 20
queryYesAuthor name to search for, up to 200 characters
offsetNoZero-based result offset, below 10000; defaults to 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden — and it does meaningful work by disclosing the one-page return payload, page-size range, and the important caveat that private/opt-out authors are filtered out so a page may be shorter than limit. Missing rate-limit or matching-semantics detail keeps it from a 5.

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 action and result shape, then pagination, then the exclusion caveat — a sensible order. It is one dense paragraph with no filler, though the field enumeration is slightly list-like and could be tightened.

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 no annotations and no output schema, the description steps up by naming the return fields, the paging model, and the privacy-exclusion behavior that affects page completeness. An agent has enough to call it and interpret a short page; only total-count and exact-match semantics are absent.

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 parameter documentation is largely handled structurally. The description adds value beyond the schema by explaining the limit/offset paging model operationally and introducing next_offset as the continuation mechanism, which the schema never mentions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Search Wattpad authors by name') and enumerates the returned fields, which helps an agent confirm it is a user-lookup tool. It does not, however, explicitly distinguish itself from siblings like wattpad_search (story search) or wattpad_user (single-profile fetch), leaving the differentiation to inference.

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

Usage Guidelines3/5

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

The query-to-authors framing implies when to use it, and 'advance with next_offset' gives forward guidance. But there is no explicit when-not, no mention of how it differs from wattpad_user for a known username, and no prerequisite context.

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