releasesReturn recent or upcoming streaming releases on Watchmode; filter by date range, streaming source IDs, content type, and region. Use to track new additions to services.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| types | No | ||
| regions | No | ||
| end_date | No | ||
| source_ids | No | ||
| start_date | No | ||
| source_types | No | ||
| regions_pricing | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "end_date": "2024-01-31",
+ "start_date": "2024-01-01"
+ },
+ {
+ "limit": 50,
+ "regions": "US",
+ "start_date": "2024-02-01",
+ "types": "movie"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "description": "Recent or upcoming releases matching criteria",
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false) already cover safety and side effects. The description adds behavioral context by specifying 'recent or upcoming' releases, which is not in annotations. No contradictions.
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?
Two sentences, front-loaded with purpose then usage. No redundancy. Every sentence contributes value.
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?
Despite having an output schema, the description does not fully cover the 8 parameters (missing 3). It provides adequate but incomplete guidance for a multi-parameter tool.
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?
Schema has 0% description coverage, so description must compensate. It explains date range, source_ids, types, regions but omits limit, source_types, regions_pricing. Partial coverage; adds value for some parameters but not all.
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 verb 'Return' and the resource 'releases', and specifies filtering dimensions (date range, source IDs, content type, region). It distinguishes this tool from sibling tools like genres or title_search by focusing on release tracking.
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 advises 'Use to track new additions to services', giving a clear use case. It does not explicitly state when not to use or compare to alternatives, but the context and sibling names provide some differentiation.
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.