Related Servers

The surface contains many near-duplicate read endpoints that differ only by path parameterization: get_users_by_id_ratings vs get_users_by_id_ratings_by_type_by_rating vs get_users_by_id_ratings_movies/shows/episodes, list_lists_popular vs get_lists_popular_by_type, get_sync_watchlist_by_type_by_sort_by_by_sort_how vs get_users_by_id_watchlist_movies_by_sort vs get_users_by_id_watchlist_by_type_by_sort_by_by_sort_how, and get_shows_by_id_seasons_by_season vs get_shows_by_id_seasons_by_season_info. Each maps to a distinct API endpoint, but an agent has to parse deep path-shaped names to tell them apart, which invites misselection.

Most tools follow a mechanical verb_path pattern (get_movies_by_id_watchnow_by_country), which is at least predictable, but several reads use bare list_ names (list_team, list_networks, list_watchnow_sources, list_users_blocked, list_users_settings) while equivalent reads elsewhere use get_*_by_*. A handful of hand-written tools (start_authentication, finish_authentication, get_result_page) use a totally different, more human convention, so conventions are mixed.

339 tools is an extreme over-expansion for a media-tracking domain; the vast majority are one-to-one wrappers of REST paths with heavy parameterized duplication. This far exceeds what an agent can navigate reliably and guarantees tool-selection noise.

Coverage mirrors the full Trakt API: auth, movies/shows/seasons/episodes/people, calendars, search, lists, comments, notes, sync (collection, history, ratings, watchlist, favorites, playback), recommendations, social, Plex and streaming connections. CRUD is present for user data, lists, comments, and notes, with no obvious dead ends.