Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wattpad_part_comments

Fetch paginated public reader comments for a Wattpad chapter by numeric chapter ID, returning comment text, commenter details, reply info, links, and timestamps.

Instructions

List reader comments on a Wattpad chapter. Returns one page of the public reader comments on a Wattpad chapter, newest first: id, text, commenter username and avatar, reply count, whether it is a reply, parent id, link and creation time. part_id is the numeric chapter id from wattpad-story-parts. limit is 1 to 100 (default 20) and offset pages the list; next_offset is absent on the last page. A chapter with no comments, or an unknown chapter, returns an empty list.

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, 1 to 100; defaults to 20
offsetNoZero-based result offset, below 100000; defaults to 0
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

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers: it specifies newest-first ordering, documents the returned fields, explains pagination termination via next_offset absence, and states empty-list behavior for no-comment or unknown chapters. This is rich, behavior-level detail beyond the schema.

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?

Four dense sentences, front-loaded with purpose and scope, then return shape, parameter sourcing, and pagination/empty behavior. Every sentence contributes useful information without filler.

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?

No output schema exists, so the description compensates by enumerating returned fields and describing pagination termination and empty results. For a three-parameter read-only listing tool, this is complete enough for correct invocation.

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%, and the schema already documents part_id origin, limit range/default, and offset semantics. The description largely repeats those points and adds little parameter-specific meaning beyond the schema baseline.

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 and resource ('List reader comments on a Wattpad chapter') and scopes it to a chapter. It is immediately distinguishable from sibling tools like wattpad_story_parts or wattpad_part.

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 clear context for when to use it by explaining part_id comes from wattpad-story-parts, and clarifies that empty/unknown chapters return an empty list. It lacks explicit when-not-to-use guidance, but there are no competing comment-listing siblings.

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