Skip to main content
Glama
rollecode

Trakt MCP server

by rollecode

get_lists_by_id_items_movie_show

Read-onlyIdempotent

Fetch movies and shows from a Trakt list by ID, applying filters like genre, year, ratings, and watch status. Sort and page through results to locate specific titles.

Instructions

Get media list items.

GET /lists/{id}/items/movie,show

Args: id: The id/slug of the resource. extended: Extended information to include in the response. sort_by: The field to sort by sort_how: The direction to sort in 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. ignore_watched: Ignore watched items. ignore_collected: Ignore collected items. ignore_watchlisted: Ignore watchlisted items. page: The page number to retrieve limit: The number of items per page, can be a number or the value all

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
pageNo
limitNo
yearsNo
genresNo
ratingsNo
sort_byNo
end_dateNo
extendedNo
runtimesNo
sort_howNo
watchnowNo
countriesNo
subgenresNo
start_dateNo
certificationsNo
ignore_watchedNo
ignore_collectedNo
ignore_watchlistedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds useful pagination and watchnow filter semantics, but it does not disclose auth requirements, rate limits, or any notable response 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 endpoint is front-loaded and the parameter list is scannable. The length is justified by 19 parameters, though several placeholder lines like 'genres: Query parameter' add little value.

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?

The output schema covers return shape and the annotations cover safety, but for a 19-parameter endpoint the description still lacks value enums, date formats, sort field options, and sibling-selection guidance. It is minimally viable but not fully complete.

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?

With schema description coverage at 0%, the Args block carries the documentation burden. It gives real meaning to id, sort, watchnow, ignore_* flags, page, and limit, but many parameters are only described as 'Query parameter' with no format, allowed values, or examples, leaving meaningful gaps.

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?

The description opens with a clear verb and resource ('Get media list items') and gives the exact endpoint path, so the operation is identifiable. However, it does not explicitly call out how this differs from the movie-only, show-only, or episode/season sibling tools beyond the endpoint suffix.

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?

There is no guidance on when to use this tool versus the many sibling list-item tools. No alternatives, exclusions, or selection criteria 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

Other Tools