List Wattpad story languages with numeric IDs and native-script names to select valid values for the language parameter in Wattpad searches.
List Wattpad story languages. Returns the story languages Wattpad's search can filter by, each with its numeric id and native-script name (50 at the time of writing). These ids are the values the language parameter of wattpad-search takes.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.16Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full burden and does well: it discloses the return shape (numeric id plus native-script name) and an approximate cardinality (~50 at time of writing). It does not discuss ordering, caching, or whether the list is paginated, which is a minor gap for a zero-argument lookup.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three tight sentences: purpose first, return content second, downstream consumption third. Every sentence adds information and nothing is repeated from structured fields.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, so the description must describe the return value, and it does supply field names and rough size. For a parameterless reference lookup, this is sufficient for an agent to call it and use the result correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes no parameters, so the baseline is 4. The description usefully explains what the returned ids mean and where they are consumed (the language parameter of wattpad-search), which is not derivable from an empty schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('List Wattpad story languages') and immediately scopes it to the values Wattpad search can filter by. An agent can tell this apart from wattpad_search and wattpad_categories without inspecting the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly frames the tool as the source of the values for the language parameter of wattpad-search, which tells the agent when to call it in a workflow. It stops short of stating exclusions or naming a competing alternative, but the workflow linkage is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.