Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

wattpad_part_comments

Read-only

List the public reader comments on a Wattpad chapter and return each comment's text, commenter username, reply count, whether it is a reply and its creation time. Use this to read audience reaction to a chapter after getting the chapter id from wattpad_story_parts; page with next_offset, and an unknown chapter returns an empty list.

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": {
      "part_id": "<part_id>"
    },
    "name": "wattpad_part_comments"
  }
}

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

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

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds real value by noting comments are public and that an unknown chapter returns an empty list rather than an error. Minor issue: it says 'page with next_offset' while the input parameter is named 'offset', which could send an agent looking for a nonexistent parameter.

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 sentences with zero filler: the first front-loads what is returned, the second front-loads usage, prerequisite and edge-case behavior. Every clause carries information an agent needs.

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?

An output schema exists, so the description need not explain return structure, and it still summarizes the key fields. Annotations cover the safety profile. The only residual gap is the 'next_offset' vs 'offset' wording, which slightly muddies the paging instruction for a 3-parameter tool.

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%, with part_id, limit (1-100, default 20) and offset (zero-based, <100000) all documented in the schema. The description repeats the chapter-id provenance but adds no syntax or format detail beyond the schema, so the 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 (List) and resource (public reader comments on a Wattpad chapter) and enumerates the returned fields (text, username, reply count, is-reply, creation time). It explicitly separates itself from the sibling wattpad_story_parts by noting that tool supplies the chapter id.

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: use it to read audience reaction to a chapter, and a prerequisite (obtain the chapter id from wattpad_story_parts first), plus paging guidance. It does not name a when-not-to-use case or a direct alternative comment source, so it falls short of a 5.

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