Orca MCP

tv_episode

Read-onlyIdempotent

One episode in full: title, overview, airdate, runtime, rating, still, director, writer, guest stars. Accepts show title, TMDB id or IMDb id - provide only one - plus season and episode numbers. Series only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tv_episode"
  }
}

Input Schema

Name	Required	Description	Default
`id`	No	Numeric TMDB series id.
`query`	No	Show title, e.g. 'breaking bad'. Use this OR id OR imdb_id (only one).
`season`	No	Season number (default 1).
`episode`	No	Episode number (default 1).
`imdb_id`	No	IMDb id like tt0903747.
`language`	No	ISO language like en-US or fa-IR.	en-US

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 15, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful output-field context but does not disclose behavior such as missing-result handling or language defaults; this is acceptable given the strong annotations but not especially rich.

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 tight sentences with no filler. The output fields are front-loaded, followed by the input-selection rule, making the definition easy to scan and immediately operational.

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?

For a read-only single-episode lookup with 100% schema coverage, the description covers the main output fields, the accepted identifiers, and the navigation coordinates (season/episode). It doesn't mention language or defaults, but those are fully specified in the schema, so nothing critical is missing for correct invocation.

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 the schema already documents all six parameters. The description adds the useful 'provide only one' exclusivity constraint among id, query, and imdb_id, but otherwise does not need to repeat parameter details.

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?

States a specific verb and resource: 'One episode in full' followed by a clear list of returned fields. It also specifies 'Series only,' which distinguishes it from movie or season-level tools and helps an agent separate it from the plural tv_episodes sibling.

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?

Clearly says which identifier forms can be used (show title, TMDB id, or IMDb id) and instructs to provide only one, plus season and episode numbers. It does not explicitly name sibling tools like tv_episodes or tv_season as alternatives, but the 'One episode' and 'Series only' wording makes the intended scope evident.

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

All Orca MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?