Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wattpad_user

Retrieve a Wattpad author's public profile from a username or profile link, including bio, avatar, location, follower counts, votes, story and reading-list counts, and join date.

Instructions

Get a Wattpad author profile. Returns a Wattpad author's public profile: username, display name, bio, avatar, location, website, verified and ambassador flags, follower and following counts, votes received, published story count, reading list count and join date. username is the name from the author's wattpad.com/user/ link, case-insensitive. Authors with a private profile or who have opted out of crawling are not returned. An unknown author returns not found.

Input Schema

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

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?

With no annotations provided, the description carries the behavioral burden well: it lists returned fields, notes that private or opted-out authors are not returned, and states that an unknown author returns not found. It could be strengthened by explicitly confirming the read-only nature and any authentication or rate-limit expectations.

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?

The description is front-loaded with purpose, then return fields, parameter semantics, and edge cases. The field enumeration earns its place because there is no output schema, and no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read tool with no output schema, the description is complete: it explains what is returned, how the username is identified, and what happens for private, opted-out, or unknown authors. An agent has enough information to call it correctly.

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 already 100%, so the baseline is 3, but the description adds useful semantics: the username comes from a wattpad.com/user/ link and is case-insensitive. It does not repeat the schema's @name alternative, but the added case-insensitivity detail is meaningful.

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?

The description states a specific verb and resource: 'Get a Wattpad author profile,' and enumerates the public profile fields returned. It is clear what the tool does, but it does not explicitly differentiate itself from nearby siblings such as wattpad_search_users or wattpad_user_stories.

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

Usage Guidelines2/5

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

The description explains how to format the username but gives no explicit guidance on when to use this tool versus alternatives. It does not mention using wattpad_search_users when only a display name is known, nor does it state when to prefer wattpad_user_stories.

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