Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

wattpad_search_users

Read-only

Search Wattpad authors by name and return each match's username, display name, bio, avatar, verified flag, published story count and followers. Use this to find an author when you only have a name; private profiles and authors who opted out of crawling are left out, and you page with next_offset.

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": {
      "query": "<query>"
    },
    "name": "wattpad_search_users"
  }
}

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

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/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint) and open-world reach, and the description adds real behavioral facts: private profiles and crawl-opted-out authors are silently omitted, and paging is done via next_offset. It does not state a result cap or rate limit, but the exclusion and pagination notes are meaningful additions beyond the annotations.

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?

Two tight clauses: the return contract first, then the usage/exclusion/paging note. Every sentence carries information an agent would otherwise have to infer.

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 annotations and an output schema present, the description only needs to add scope and caveats, which it does (name-only lookup, privacy exclusions, paging). A named alternative tool for the follow-up lookup would make it fully self-sufficient.

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 query/limit/offset are already documented; the description only hints at pagination via next_offset without reconciling it against the numeric offset parameter in the schema. Baseline 3 applies since the schema does the heavy lifting.

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 concrete verb+resource (search Wattpad authors by name) and enumerates exactly what each match returns, so the output shape is clear before opening the schema. It distinguishes itself from the username-based sibling only implicitly, via 'when you only have a name', without naming wattpad_user.

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?

Gives a clear trigger condition ('find an author when you only have a name'), which implies the companion tool should be used once a username is known. No explicit when-not or named alternative, so it stops short of full routing guidance.

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