Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wattpad_part

Retrieve a Wattpad chapter's metadata by numeric chapter ID, including title, link, word count, reads, votes, comments, dates, and parent story details; chapter text is not returned.

Instructions

Get a Wattpad chapter. Returns one Wattpad chapter's metadata: id, title, link, word count, reads, votes, comments, length, dates and the story it belongs to (id and title). part_id is the numeric chapter id from wattpad-story-parts. A chapter that does not exist returns not found. Chapter text is never returned.

Input Schema

NameRequiredDescriptionDefault
part_idYesNumeric chapter id from the id field of wattpad-story-parts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description does a good job disclosing behavior: it lists the returned metadata fields, states that a non-existent chapter returns not found, and explicitly says chapter text is never returned. It does not mention auth or rate limits, but for a simple public getter the key behavioral traits are covered.

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 the core action and then efficiently covers return fields, parameter origin, not-found behavior, and the important limitation that text is never returned. Every sentence adds useful information without waste.

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 single-parameter getter with no output schema and no annotations, the description provides enough context: it lists the metadata fields returned, explains the id source, covers the not-found case, and clarifies that chapter text is excluded.

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 description coverage is 100%, so the schema already fully documents part_id. The description reinforces that it is the numeric chapter id from wattpad-story-parts but does not add format or meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 chapter' and specifies that it returns chapter metadata. It distinguishes the resource from a story by noting it returns the story the chapter belongs to, though it does not explicitly contrast itself with sibling tools beyond referencing wattpad-story-parts for the id.

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 description implies a workflow by saying part_id comes from wattpad-story-parts, which helps an agent know where to get the id. However, it does not explicitly state when to use this tool vs alternatives such as wattpad_story or wattpad_story_parts.

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