Skip to main content
Glama

Trakt

by io.github.pipeworx-io

Get Movie

get_movie
Read-onlyIdempotent

Fetch a movie record from Trakt by Trakt ID, slug, or IMDB/TMDB ID. Pass extended="full" to include plot, runtime, genres, rating, certification, and release year.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYestrakt ID, slug, or IMDB/TMDB ID
extendedNofull | metadata | images (default omitted = base record)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoTrakt, IMDB, TMDB, Slug IDs
yearNoRelease year
titleNoMovie title
votesNoNumber of votes
genresNoList of genre slugs
peopleNoCast and crew information
ratingNoAverage rating
runtimeNoRuntime in minutes
taglineNoMovie tagline
languageNoLanguage code
overviewNoPlot summary
releasedNoRelease date
translationsNoAvailable translations

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, and non-destructive behavior. The description adds value by explaining the effect of the extended parameter and that it fetches from Trakt. 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.

Conciseness5/5

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

Two sentences: first establishes core purpose, second explains optional functionality. No wasted words, essential information front-loaded.

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

Completeness5/5

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

Given the schema covers parameter descriptions, annotations cover safety, and an output schema exists, the description is complete. It explains input variants and extended option, which is all that's needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds specific meaning: it lists the fields included with extended='full' (plot, runtime, genres, etc.). This goes beyond the schema's enum values. The examples also illustrate usage.

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 the verb 'Fetch', the resource 'movie record', and the source 'Trakt'. It specifies multiple ID types (Trakt ID, slug, IMDB/TMDB ID) and optional extended parameter. This clearly distinguishes it from sibling tools like get_episode or get_show.

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

Usage Guidelines4/5

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

The description explicitly tells when to use the extended parameter to get additional fields. While it doesn't contrast with alternatives, the sibling context makes it clear this is for movies. It could mention scenarios where not to use it, but it's sufficient.

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

All Trakt toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation2/5

The tool set has significant overlap among query and research tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, bet_research) and among entity/company tools (entity_profile, compare_entities, recent_changes). Despite detailed descriptions, an agent would struggle to select the correct tool without careful reading, especially for nuanced differences.

Naming Consistency2/5

Tool naming is inconsistent: some start with verbs (ask_, generate_, validate_, scan_, subscribe) while others are nouns (entity_profile, popular, trending, search, recent_alerts, recent_changes). The snake_case style is consistent, but the verb_noun pattern is not, making predictions of tool names difficult.

Tool Count3/5

38 tools is on the high side for a single server, but the scope is broad (general query, research, Trakt, subscriptions, memory). The count is appropriate for the wide range of functionality, though some tools could be merged to reduce cognitive load.

Completeness4/5

The tool set covers a very wide range of tasks: querying, research, entity profiles, comparisons, subscriptions, memory, Trakt operations, etc. For the Trakt domain, it has all essential operations (search, get, list, trending). The Pipeworx side has a comprehensive set for data access, grounding, and validation. Minor gaps exist (e.g., no update for subscriptions), but overall it is well-covered.

Resources