TMDB MCP Server

TV Videos

tv_videos

Retrieve video content for TV shows using their TMDB ID to access trailers, clips, and promotional media.

Instructions

Get TV show videos by 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": {
      "tv_id": "<tv_id>"
    },
    "name": "tv_videos"
  }
}

Input Schema

Name	Required	Description	Default
`tv_id`	Yes	TMDB TV show ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Apr 21, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action without disclosing behavioral traits such as rate limits, authentication needs, error handling, or what 'videos' entails (e.g., trailers, clips). It's minimal and lacks critical operational context.

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 a single, efficient sentence with zero waste, front-loaded with the core action. It's appropriately sized for a simple tool, earning its place without redundancy.

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

Completeness2/5

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

Given no annotations, no output schema, and a simple input schema, the description is incomplete. It doesn't explain what 'videos' includes, potential response formats, or any constraints, leaving gaps for a tool that likely returns structured data.

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%, with the parameter 'tv_id' documented as 'TMDB TV show ID'. The description adds no additional meaning beyond this, as it only restates 'by ID'. Baseline 3 is appropriate since the schema fully covers the parameter.

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?

The description clearly states the action ('Get') and resource ('TV show videos'), specifying retrieval by ID. It distinguishes from siblings like 'tv_details' or 'movie_videos' by focusing on videos specifically, though it doesn't explicitly contrast with 'tv_credits' or other video-related tools.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'tv_details' (which might include videos) or 'movie_videos' (for movies). The description implies usage when needing videos for a TV show by ID, but lacks explicit context or exclusions.

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