title_seasonsSeasons + episodes for a Watchmode TV show ID. Returns episode count, season number, year. Use after title_search to enumerate a show's structure.
| Name | Required | Description | Default |
|---|---|---|---|
| title_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "title_id": "12345"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "description": "Season information for a title",
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds context about return fields (episode count, season number, year) and a usage hint, which complements the annotations without contradiction.
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?
The description is two sentences (22 words), front-loading the core function and then providing return details and a usage hint. Every sentence adds value with no redundancy.
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?
Given the simple tool (one parameter, no nested objects) and the presence of an output schema, the description is complete. It explains what the tool does, when to use it, and what it returns, enabling an agent to invoke it 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?
Although schema description coverage is 0%, the single parameter 'title_id' is contextualized in the description as a 'Watchmode TV show ID' and tied to the output of title_search. This compensates for the lack of schema descriptions.
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?
The description clearly states that the tool returns seasons and episodes for a Watchmode TV show ID, specifying the output fields (episode count, season number, year). It distinguishes itself from siblings like title_search and title_detail by indicating it is used after title_search to enumerate structure.
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?
The description explicitly advises 'Use after title_search to enumerate a show's structure,' providing clear when-to-use guidance. It does not list alternatives or when-not-to-use, but the advice is sufficient for an agent to decide correctly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.