Skip to main content
Glama

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.

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": {
      "show_id": "<show_id>"
    },
    "name": "tvmaze_get_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
show_idYesTVmaze show id, from tvmaze_search_shows, tvmaze_lookup_show, or tvmaze_get_schedule.
timezoneNoIANA 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

NameRequiredDescriptionDefault
showNoFull show profile.
errorNoPresent when the call failed. Absent on success.
noticeNoGuidance when a Running show has no scheduled next episode. Absent otherwise.
seasonsNoEvery season TVmaze records, in order. Pass a season number to tvmaze_get_episodes.
timezoneNoIANA timezone the episode times were rendered in.
next_episodeNoThe next episode scheduled to air. Absent when none is scheduled — a Running show between seasons has no next episode.
previous_episodeNoThe most recently aired episode. Absent for a show that has not premiered.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedOutput schema / properties / next_episode / properties / airdate
      Added value: +{
      +  "description": "TVmaze date label (YYYY-MM-DD): the programming day or announced release date. Preserve it as a label without combining it with a clock time.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / previous_episode / properties / airdate
      Added value: +{
      +  "description": "TVmaze date label (YYYY-MM-DD): the programming day or announced release date. Preserve it as a label without combining it with a clock time.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / seasons / items / properties / network
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Broadcast or cable network, when recorded.",
      +  "properties": {
      +    "country": {
      +      "description": "ISO 3166-1 alpha-2 country of this carrier.",
      +      "type": "string"
      +    },
      +    "name": {
      +      "description": "Carrier name as TVmaze records it.",
      +      "type": "string"
      +    },
      +    "timezone": {
      +      "description": "IANA timezone recorded for this carrier.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "name"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / seasons / items / properties / web_channel
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Streaming service, when recorded.",
      +  "properties": {
      +    "country": {
      +      "description": "ISO 3166-1 alpha-2 country of this carrier.",
      +      "type": "string"
      +    },
      +    "name": {
      +      "description": "Carrier name as TVmaze records it.",
      +      "type": "string"
      +    },
      +    "timezone": {
      +      "description": "IANA timezone recorded for this carrier.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "name"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / show / properties / network
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Broadcast or cable network, when recorded.",
      +  "properties": {
      +    "country": {
      +      "description": "ISO 3166-1 alpha-2 country of this carrier.",
      +      "type": "string"
      +    },
      +    "name": {
      +      "description": "Carrier name as TVmaze records it.",
      +      "type": "string"
      +    },
      +    "timezone": {
      +      "description": "IANA timezone recorded for this carrier.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "name"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / properties / show / properties / schedule_days / description
      Previous value: -"Weekdays the show airs in its regular slot, e.g. [\"Monday\"]. Empty for a streaming release with no weekly slot."New value: +"Programming weekdays for the usual premiere slot, e.g. [\"Monday\"]. A late-night slot can fall on the next calendar day. Empty when no weekly slot is recorded."
    • 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\"; schedule_timezone names that clock when known. Absent when there is no fixed slot."New value: +"TVmaze’s usual premiere slot as a local 24-hour clock label, e.g. \"22:00\"; schedule_timezone names the selected carrier’s clock when known. Absent when there is no fixed slot."
    • changedOutput schema / properties / show / properties / schedule_timezone / description
      Previous value: -"IANA timezone of the selected channel’s recurring schedule. Absent when the channel does not provide one."New value: +"IANA timezone of the selected carrier for TVmaze’s usual premiere slot. The network is selected when both carriers are recorded. Absent when the selected carrier does not provide a timezone."
    • addedOutput schema / properties / show / properties / web_channel
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Streaming service, when recorded.",
      +  "properties": {
      +    "country": {
      +      "description": "ISO 3166-1 alpha-2 country of this carrier.",
      +      "type": "string"
      +    },
      +    "name": {
      +      "description": "Carrier name as TVmaze records it.",
      +      "type": "string"
      +    },
      +    "timezone": {
      +      "description": "IANA timezone recorded for this carrier.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "name"
      +  ],
      +  "type": "object"
      +}
  2. Changed3 schema fields changed
    • 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"
      +}
  3. Changed4 schema fields changed
    • 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."
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered; the description adds that previous/next episode are only present 'when the source has them', warning the agent about optional fields. It does not mention rate limits, caching, or upstream latency, which for an open-world remote API would be the remaining useful 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?

Two sentences, zero filler: the first defines contents, the second handles routing to alternatives. Front-loaded with the action and resource before the disambiguation detail.

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?

With an output schema present, return-value detail is unnecessary, and the description covers scope, when to call, where the id comes from, and the optionality caveat. Nothing an agent needs to invoke it correctly is missing.

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%, so both show_id and timezone are fully documented in the schema, establishing the baseline of 3. The description adds no meaning about the timezone parameter's effect on rendering previous/next air times, so it does not exceed what the schema already provides.

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 ('Fetch a television show by its TVmaze id') and enumerates the payload: full profile, weekly broadcast slot, season list, previous/next episode. That scope makes it distinguishable from tvmaze_get_episodes and tvmaze_get_cast, which it names directly.

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?

Gives an explicit entry condition ('entry point for an id returned by tvmaze_search_shows or tvmaze_lookup_show') and two explicit exclusions routing to tvmaze_get_episodes and tvmaze_get_cast. An agent can pick correctly without opening any schema.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.