Trakt MCP server

Overview Schema Source Related Servers Discussions Admin

list_shows_hot

Read-onlyIdempotent

Find popular TV shows by genre, streaming service, country, and more. Filter hot shows by ratings, years, runtimes, and watch status to discover what to watch.

Instructions

Get hot shows.

GET /shows/hot

Args: extended: Extended information to include in the response. watchnow: Use "favorites" for streaming on a favorite service of the user. Use "any" for streaming on any service in the user's country. Use "any_all" for streaming on any service in all countries. Use "free" for streaming for free in the user's country. Use "free_all" for streaming for free in all countries. Use "subscriptions" for streaming on any subscription service (Netflix, Hulu, etc) in the user's country. Use "subscriptions_all" streaming on any subscription service in all countries genres: Query parameter. subgenres: Query parameter. years: Query parameter. ratings: Query parameter. start_date: Query parameter. end_date: Query parameter. runtimes: Query parameter. countries: Query parameter. certifications: Query parameter. page: The page number to retrieve limit: The number of items per page. Defaults and maximums vary by endpoint. When pagination parameters are omitted, a low default limit is applied (often 10). When a limit is provided, it is capped at the endpoint maximum (often 250); higher values are clamped rather than rejected. ignore_watched: Ignore watched items. ignore_collected: Ignore collected items. ignore_watchlisted: Ignore watchlisted items.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No
`limit`	No
`years`	No
`genres`	No
`ratings`	No
`end_date`	No
`extended`	No
`runtimes`	No
`watchnow`	No
`countries`	No
`subgenres`	No
`start_date`	No
`certifications`	No
`ignore_watched`	No
`ignore_collected`	No
`ignore_watchlisted`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 15, 2026

TDQS

B3.2/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish read-only, idempotent, non-destructive behavior. The description adds some behavioral context, such as pagination defaults and clamping, but does not explain the ranking semantics of 'hot' or other runtime behavior; it does not contradict the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is organized as a compact argument list and front-loads the core purpose in a single sentence. The repeated 'Query parameter' placeholders and the verbose watchnow block add some bulk, but the structure is serviceable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter endpoint with no schema descriptions, the definition covers parameter names and a few key behaviors but leaves most filter formats unspecified. The output schema and annotations cover return shape and safety, so the missing value formats are the main completeness gap.

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 description coverage is 0%, so the description must carry the parameter documentation. It provides genuinely useful semantics for watchnow (enumerated values) and limit (defaults and clamping), but the majority of filter parameters are dismissed as 'Query parameter' with no format or value guidance, so it only partially compensates for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States that the tool returns hot shows and gives the exact endpoint (GET /shows/hot), so the verb and resource are clear. However, it does not explain how 'hot' differs from sibling list endpoints such as list_shows_popular, list_shows_trending, or list_shows_anticipated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given about when to choose this endpoint over the many sibling list endpoints (popular, trending, anticipated). The description only names the action and parameters, leaving selection to inference from the tool name.

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

Deploy Server