Trakt MCP server

by rollecode

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

list_shows_trending

Read-onlyIdempotent

Find trending TV shows by filtering on genre, year, rating, country, and streaming availability to see what's popular.

Instructions

Get trending shows.

GET /shows/trending

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

A3.7/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true and idempotentHint=true, and the description aligns by describing a read operation. The description adds behavior details like pagination defaults ('Defaults and maximums vary by endpoint...') and the watchnow parameter's various modes, which are beyond what annotations provide. 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.

Conciseness3/5

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

The description is long and repetitive, listing every parameter in a mixed format: some have full explanations, others just say 'Query parameter'. The useful info about watchnow and pagination is buried amidst the parameter list. It could be more concise and front-load the most important behavioral details.

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 read-only list tool with many optional filters, the description explains key behaviors (watchnow modes, pagination limits) and the endpoint is clear. However, it lacks guidance on how filters interact or which filters are typically used together. Given the output schema exists, return values are covered, but the description is not fully complete for an agent to know exactly how to construct effective requests.

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?

The description provides detailed semantics for the watchnow parameter and the limit/pagination behavior. For other parameters (genres, years, etc.), it only says 'Query parameter', which adds no value beyond the schema. With 16 parameters and 0% schema coverage, the description partially compensates but many parameters remain underdocumented.

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

Purpose5/5

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

The description clearly states 'Get trending shows' and includes the endpoint 'GET /shows/trending', distinguishing it from sibling tools like list_shows_popular or list_shows_hot. The verb 'Get' and resource 'trending shows' are specific.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool versus other list tools like list_media_trending or list_shows_popular. However, the tool name and endpoints imply it is for trending shows, and the description provides filter options for how to narrow results. No exclusions or alternatives are mentioned.

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

Deploy Server