list_titlesBrowse and filter the Watchmode title catalog by streaming source, genre, network, type (movie/TV), release date range, and sort order; paginates with page + limit.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| limit | No | ||
| types | No | ||
| genres | No | ||
| regions | No | ||
| sort_by | No | ||
| networks | No | ||
| source_ids | No | ||
| source_types | No | ||
| release_date_end | No | ||
| release_date_start | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "limit": 20,
+ "regions": "US",
+ "types": "tv"
+ },
+ {
+ "genres": "action,drama",
+ "limit": 25,
+ "page": 1,
+ "sort_by": "release_date",
+ "source_types": "subscription"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "description": "Paginated list of titles from catalog with filters",
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds behavioral context beyond annotations by mentioning pagination (page + limit) and the range of filtering options, which helps the agent understand expected behavior.
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 a single, well-structured sentence that immediately conveys the core functionality. It is front-loaded with action verbs and keeps content minimal, avoiding redundancy with 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?
Given the tool's 11 parameters and no schema descriptions, the description is too brief. It does not explain how each parameter interacts, default values, or response format (though output schema exists). The agent would lack crucial details for complex queries.
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 description enumerates broad categories of parameters (streaming source, genre, network, type, date range, sort order) but provides no detail on valid values or format for any parameter. With 11 parameters and 0% schema description coverage, the description is insufficient to guide parameter usage effectively.
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 the tool's purpose: to browse and filter a title catalog by multiple criteria. It uses specific verbs ('browse', 'filter') and describes the resource ('Watchmode title catalog') and key filtering dimensions, distinguishing it from siblings like 'title_search' which likely handles name-based search.
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 implies usage for listing and filtering titles but does not explicitly state when to use this tool versus alternatives like 'title_search' or 'releases'. There is no guidance on prerequisites or exclusions, which is a gap given the number of sibling tools.
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.