tvmaze-mcp-server

Tvmaze Get Show

tvmaze_get_show

Read-onlyIdempotent

Fetch a television show by its TVmaze id: full profile, weekly broadcast slot, season list, and the previous and next episode when the source has them. This is the entry point for an id returned by tvmaze_search_shows or tvmaze_lookup_show. For the episode list itself use tvmaze_get_episodes, and for credits use tvmaze_get_cast.

Input Schema

Name	Required	Description	Default
`show_id`	Yes	TVmaze show id, from tvmaze_search_shows, tvmaze_lookup_show, or tvmaze_get_schedule.
`timezone`	No	IANA timezone name for rendering the previous and next episode air times, e.g. "America/Los_Angeles" or "Europe/London". Defaults to the server-configured timezone.

Output Schema

Name	Required	Description
`show`	No	Full show profile.
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Guidance when a Running show has no scheduled next episode. Absent otherwise.
`seasons`	No	Every season TVmaze records, in order. Pass a season number to tvmaze_get_episodes.
`timezone`	No	IANA timezone the episode times were rendered in.
`next_episode`	No	The next episode scheduled to air. Absent when none is scheduled — a Running show between seasons has no next episode.
`previous_episode`	No	The most recently aired episode. Absent for a show that has not premiered.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 16, 2026

changedOutput schema / properties / seasons / items / properties / channel / description

Previous value: -"Network or streaming service that carried this season, when it differs from the show."New value: +"Network or streaming service that carried this season, including when it matches the show."

changedOutput schema / properties / show / properties / schedule_time / description

Previous value: -"Regular slot start time in the channel’s local 24-hour clock, e.g. \"22:00\". Absent when there is no fixed slot."New value: +"Regular slot start time in the channel’s local 24-hour clock, e.g. \"22:00\"; schedule_timezone names that clock when known. Absent when there is no fixed slot."

addedOutput schema / properties / show / properties / schedule_timezone

Added value: +{
+  "description": "IANA timezone of the selected channel’s recurring schedule. Absent when the channel does not provide one.",
+  "type": "string"
+}

Changed4 schema fields changedSep 22, 2026

changedOutput schema / properties / next_episode / properties / local_date / description

Previous value: -"Calendar date the episode airs, in the requested timezone, ISO 8601 (YYYY-MM-DD)."New value: +"Calendar date the episode airs, ISO 8601 (YYYY-MM-DD). When time_known is true, the date in the requested timezone. When time_known is false, the source’s own announced air date, not timezone-converted — the same in every timezone."

changedOutput schema / properties / next_episode / properties / type / description

Previous value: -"Episode classification: \"regular\", \"significant_special\", or \"insignificant_special\". Anything other than \"regular\" is a special, and specials are excluded from a whole-run listing unless include_specials is set."New value: +"Episode classification: \"regular\", \"significant_special\", or \"insignificant_special\". Anything other than \"regular\" is a special; tvmaze_get_episodes leaves specials out unless include_specials is set."

changedOutput schema / properties / previous_episode / properties / local_date / description

Previous value: -"Calendar date the episode airs, in the requested timezone, ISO 8601 (YYYY-MM-DD)."New value: +"Calendar date the episode airs, ISO 8601 (YYYY-MM-DD). When time_known is true, the date in the requested timezone. When time_known is false, the source’s own announced air date, not timezone-converted — the same in every timezone."

changedOutput schema / properties / previous_episode / properties / type / description

Previous value: -"Episode classification: \"regular\", \"significant_special\", or \"insignificant_special\". Anything other than \"regular\" is a special, and specials are excluded from a whole-run listing unless include_specials is set."New value: +"Episode classification: \"regular\", \"significant_special\", or \"insignificant_special\". Anything other than \"regular\" is a special; tvmaze_get_episodes leaves specials out unless include_specials is set."

First observedSep 20, 2026

TDQS

A4.3/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so safety and external-source behavior are covered. The description adds useful conditional phrasing ('when the source has them') that signals optional return fields and flags that this branches out to external data. It does not discuss error behavior for invalid ids, rate limits, or response shape, but the output schema exists to cover return values, so a 3 is appropriate.

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, no repetition of name or title, and the routing information is front-loaded after the one-line scope statement. Every clause earns its place by either defining scope or steering to a sibling.

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?

For a read-only lookup with an output schema and fully documented parameters, this definition is complete: it states what is fetched, when to use it, what siblings handle the rest, and that some fields may be absent. The only omission is error semantics, which is minor here.

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 100% and both parameters have descriptive text, so the schema carries the parameter burden. The description adds only an implicit link between the timezone parameter and the previous/next episode air times, which is marginal beyond the schema wording. Baseline 3 applies when the schema is fully documented.

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 uses a specific verb ('Fetch') and resource ('television show') and enumerates exactly what comes back: full profile, weekly broadcast slot, season list, previous and next episode. It also names the sibling tools covering the adjacent capabilities (tvmaze_get_episodes, tvmaze_get_cast), so an agent can separate it from tvmaze_lookup_show and tvmaze_search_shows.

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

Usage Guidelines5/5

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

It states an explicit entry condition ('the entry point for an id returned by tvmaze_search_shows or tvmaze_lookup_show') and names the alternatives for neighboring needs: episode lists go to tvmaze_get_episodes, credits to tvmaze_get_cast. Nothing is left to inference about when to select this tool.

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

All tvmaze-mcp-server 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.