Skip to main content
Glama
TMDB MCP Server

TMDB MCP Server

Search production companies

search_companies
Read-only

Resolve a production company name to its TMDB numeric ID for filtering movies or TV by company. Check origin_country and logo_url to distinguish same-name companies.

Instructions

Resolve a production company's name to its TMDB numeric id (e.g. 'A24', 'Pixar'). Feed the id into discover_movies/discover_tv via with_companies. Company names aren't unique: TMDB can have several unrelated companies with the same name (e.g. two different 'A24's, one US and one GB), so check origin_country and logo_url to tell rows apart when a name matches more than one.

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": {
      "query": "<query>"
    },
    "name": "search_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number for pagination (TMDB returns up to 20 results per page, max 500).
queryYesCompany name to look up.

Output Schema

NameRequiredDescriptionDefault
pageYes
resultsYes
total_pagesYes
total_resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.14.0
    • removedOutput schema / properties / results / items / properties / logo_url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / results / items / properties / logo_url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / results / items / properties / origin_country / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / results / items / properties / origin_country / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Addedv0.8.0

TDQS

A4.3/5.0
Behavior4/5

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

The annotations only declare readOnlyHint and openWorldHint. The description adds the useful point that company names are not unique and that origin_country and logo_url should be checked to tell rows apart when a name matches more than one. That directly prevents an agent from silently picking the wrong company. It does not cover rate limits or pagination behavior, but the annotations already cover the safety profile.

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, front-loaded with the core action and then the disambiguation caveat. Examples are inline and cheap; no sentence is padding. The progression from what the tool does, then to the downstream use, then to the ambiguity risk, is logically ordered.

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?

An output schema exists, so the description does not need to enumerate return fields. With only two parameters, full schema coverage and the ambiguity caveat, this tool has everything an agent needs to call it and interpret a multi-row result correctly.

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 description coverage is 100%, so both the query and page parameters are already documented in the schema. The description reinforces what query means by giving name examples, but adds no syntax, normalization or matching-behavior details (exact vs partial match, ordering) beyond what the schema supplies. Baseline 3.

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 opens with a specific verb and resource: resolve a production company name to its TMDB numeric id, with concrete examples ('A24', 'Pixar'). This clearly separates it from the search_movies/search_tv siblings, which look up titles rather than company identities.

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 explains the full workflow: resolve the name here, then feed the resulting id into discover_movies/discover_tv via with_companies. That is clear context for when this tool is the right step. However, it does not rule out other sources of the id (for example, whether search_multi can return company ids), so the when-not guidance is implicit.

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