Skip to main content
Glama

wattpad_story_parts

Read-only

List a Wattpad story's chapters in reading order and return each chapter's id, title, link, word count, reads, votes, comments and dates. Use this to see how a story is paced, where readers drop off and which chapters get the most votes and comments after identifying the story; an unknown story returns not found and no chapter text is returned.

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": {
      "story_id": "<story_id>"
    },
    "name": "wattpad_story_parts"
  }
}

Input Schema

NameRequiredDescriptionDefault
story_idYesNumeric Wattpad story id, such as 344352588; a wattpad.com/story link 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.3/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 useful behavioral context: an unknown story returns not found and no chapter text is returned, which tells the agent what to expect on failure and what content is excluded.

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 tightly written sentences with no waste. The core listing behavior and returned fields are front-loaded, followed by concise use-case and error behavior.

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 read-only, single-parameter list tool with an output schema, the description covers scope, return fields, error behavior, and content boundaries. Nothing an agent needs to call it correctly is missing.

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%, so the story_id parameter is fully documented in the schema. The description reinforces that the story must be identified first and that an unknown id yields not found, but it adds no syntax or format detail beyond the schema.

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?

The description uses a specific verb and resource: 'List a Wattpad story's chapters in reading order.' It clearly distinguishes this from story-level or chapter-level siblings like wattpad_story and wattpad_part by focusing on the chapter list and its per-chapter engagement metrics.

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?

It gives explicit analytical use cases: seeing pacing, reader drop-off, and which chapters get the most votes/comments. The phrase 'after identifying the story' implies a prerequisite, but no alternative tools are named or excluded.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.