TMDB MCP Server

Overview Schema Source Related Servers Discussions Admin

Search production companies

search_companies

Read-only

Resolve a production company name to its TMDB numeric ID for movie and TV discovery; use origin country and logo to distinguish companies that share a name.

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 sharing the same name (e.g. two different 'A24's, one US and one GB) — check origin_country and logo_url to tell rows apart when a name matches more than one.

Input Schema

Name	Required	Description	Default
`page`	No	1-based page number for pagination (TMDB returns up to 20 results per page, max 500).
`query`	Yes	Company name to look up.

Output Schema

Name	Required	Description	Default
`page`	Yes
`results`	Yes
`total_pages`	Yes
`total_results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.14.0Oct 24, 2026
- 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"
+]
```
Addedv0.8.0Jul 22, 2026

TDQS

A4.3/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 valuable behavioral context beyond annotations: company names are not unique, multiple TMDB rows may share a name, and origin_country plus logo_url are needed to distinguish them. It does not describe pagination behavior, but the schema covers page.

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?

The description is three tight sentences with no wasted text. The core purpose is front-loaded, followed by the downstream usage and the disambiguation warning in a logical order.

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 read-only annotations, complete parameter schema, and output schema, the description is complete enough for correct selection and invocation. It covers the purpose, the downstream integration, and the key real-world ambiguity an agent must handle when resolving company names.

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 query and page are already documented in the schema. The description adds examples for query ('A24', 'Pixar') and clarifies the disambiguation fields to check, but it does not add format or pagination semantics beyond the schema. Baseline 3 is appropriate.

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 states a specific verb and resource: resolve a production company name to its TMDB numeric id. It gives examples ('A24', 'Pixar') and clearly distinguishes the tool's output from sibling search tools by explaining that the id is for use with discover_movies/discover_tv via with_companies.

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?

It explicitly explains the downstream use: feed the returned id into discover_movies or discover_tv via with_companies. It also gives a clear warning about non-unique company names and how to disambiguate using origin_country and logo_url. It does not explicitly contrast with other sibling search tools, but the intended usage context is clear.

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