Skip to main content
Glama

Get recommendations

get_recommendations
Read-only

Fetch movies or TV shows related to a given TMDB title, using either user-behavior recommendations or genre/keyword similarity.

Instructions

Movies or shows related to a given one. source=recommendations uses TMDB user behaviour; source=similar uses genres and keywords.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "media_type": "<media_type>",
      "id": "<id>"
    },
    "name": "get_recommendations"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTMDB movie or TV show ID
pageNoResults page, 1-500. Each page holds up to 20 results.
sourceNorecommendations
languageNoResponse language as ISO 639-1 with optional ISO 3166-1 region, e.g. en-US or fr-FR. Defaults to TMDB_LANGUAGE.
media_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-obvious behavior: the results' provenance differs by source, with recommendations drawing on TMDB user behaviour and similar drawing on genres and keywords, which tells the agent why result sets differ between modes.

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 short sentences, purpose front-loaded, then the parameter semantics that matter most. No filler, no restatement of the name or title.

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

Completeness4/5

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

With read-only annotations, no output schema, and a small required set (media_type + id) documented in the schema, the definition covers what an agent needs to call it correctly. The one gap is that return shape is never stated despite pagination up to 500 pages, so an agent cannot tell what a result entry looks like or that results are paginated lists of media items.

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

Parameters5/5

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

Schema coverage is 60%, with the source enum carrying no description in the schema, and the description supplies exactly that missing meaning for both enum values, plus the underlying signal each uses. This is meaning an agent could not obtain from the schema alone.

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?

"Movies or shows related to a given one" names the resource (related movies/shows) and the operation (fetching relations for a seed item) concretely enough that an agent can distinguish it from get_movie or get_collection. The verb is implicit rather than stated ('Get' appears only in the title), and no sibling is named as an explicit alternative.

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 second sentence distinguishes the two modes of the tool (behaviour-based vs genre/keyword-based), which is useful decision guidance within the tool. It never says when to prefer this over get_movie, discover_movies, or get_trending, so guidance against alternatives is only implied.

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