Skip to main content
Glama

Find by external ID

find_by_external_id
Read-only

Look up TMDB movies, TV shows, episodes, or people by an external ID such as an IMDb or TVDB ID, with optional source and language selection.

Instructions

Look up TMDB movies, shows, episodes or people by an external ID such as an IMDb ID (tt0111161, nm0000151) or a TVDB ID.

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": {
      "external_id": "<external_id>"
    },
    "name": "find_by_external_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceNoimdb_id
languageNoResponse language as ISO 639-1 with optional ISO 3166-1 region, e.g. en-US or fr-FR. Defaults to TMDB_LANGUAGE.
external_idYesThe external ID, e.g. tt0111161

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/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 the ID formats (tt0111161, nm0000151), which is useful behavior-adjacent context, but it omits that the lookup can return any of four entity types and says nothing about not-found behavior or which additional sources beyond IMDb/TVDB are accepted.

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?

A single front-loaded sentence with no filler, and the example formats earn their space. It is arguably undersized for a tool whose source enum has eight values, but nothing is redundant.

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 resolver with no output schema, the description covers purpose and ID format but leaves the source selector and multi-type return behavior unexplained. Adequate to attempt a call, not complete enough to use confidently across all eight sources.

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?

Schema coverage is 67% with the language and external_id parameters self-documented; the description reinforces external_id formats, including the IMDb movie-vs-person prefix distinction. However, it never explains the 'source' parameter, whose enum spans eight ID systems including social handles and Wikidata, leaving the critical ID-type selection undocumented in both prose and schema.

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?

Names a specific verb (look up) and resource (TMDB movies, shows, episodes, people) plus the lookup key (external ID). An agent immediately understands this is an ID-based resolver rather than a title search, which distinguishes it from search/get_movie by mechanism, though no sibling is named explicitly.

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?

Usage is only implied: use this when you already hold an external identifier. There is no explicit statement of when to prefer this over search or get_movie, nor when-not to use it (e.g., you only have a TMDB ID or a title).

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