Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

wattpad_user

Read-only

Get a Wattpad author's public profile and return their username, display name, bio, avatar, location, website, verified flag, followers, following, votes received and published story count. Use this to size an author's audience after finding them in wattpad_search or wattpad_story; authors with a private profile or who opted out of crawling are not returned, and an unknown author returns not found.

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": {
      "username": "<username>"
    },
    "name": "wattpad_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesWattpad username from wattpad.com/user/{username}; a profile link or @name is also accepted

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

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuinely new behavioral context: private or opted-out authors are excluded and an unknown author yields not-found. No auth, rate-limit, or pagination notes, but the failure-mode disclosure is the important part for this tool.

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 the operation and its scope before the workflow hint and edge cases. The long enumeration of returned fields partly duplicates the existing output schema, which is the only real slack.

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?

For a single-parameter lookup with annotations and an output schema, the description covers purpose, precondition (found elsewhere first), and not-found behavior. Nothing needed to invoke it correctly is missing; the field list repeats what the output schema already carries.

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% and the parameter description already explains accepted formats (profile link, @name). The tool description adds no parameter-level meaning, so baseline 3 applies.

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 (get) and resource (Wattpad author's public profile), then enumerates the returned fields so the agent knows exactly what data is on offer. It is clearly distinguishable from sibling wattpad_search_users (which searches) and wattpad_user_stories (which lists stories).

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 explicit workflow context: 'Use this to size an author's audience after finding them in wattpad_search or wattpad_story.' That tells the agent when the call is appropriate and implies a prerequisite identifier. It does not mention wattpad_search_users as the alternate way to resolve a username, so the routing is clear but not exhaustive.

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