Skip to main content
Glama

Tvmaze Get Next Episode

tvmaze_get_next_episode
Read-onlyIdempotent

Report when a show’s next episode airs, converted to a viewer timezone. Accepts a TVmaze id or a show title — a title is resolved with a stricter single-match search than tvmaze_search_shows uses. A show with no scheduled next episode is reported as a miss carrying its most recent episode, which is the normal state for a series between seasons.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
showNoThe show the answer is about. Absent when the show itself could not be resolved.
errorNoPresent when the call failed. Absent on success.
foundNoTrue when a next episode is scheduled.
guidanceNoWhat to do next when no next episode was returned. Absent on a hit.
timezoneNoIANA timezone the air times were rendered in.
miss_reasonNoWhy no next episode was returned. "show_not_found" means the title or id resolved to nothing; "no_scheduled_episode" means the show exists but has nothing on the schedule.
next_episodeNoThe next scheduled episode. Absent on a miss.
previous_episodeNoThe most recently aired episode. Returned on a hit and on a "no_scheduled_episode" miss, so a between-seasons answer still says where the show left off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 / 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"
      +}
    • 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. 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."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so safety is covered. The description earns credit for disclosing a non-obvious behavior the annotations cannot express: a show with no scheduled next episode returns a miss plus its most recent episode, described as the normal between-seasons state. What it doesn't cover is behavior when a title resolves to no match at all or when TVmaze errors.

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?

Three sentences, front-loaded with the core action, then identifier handling, then the no-next-episode case. Every sentence carries distinct information with no restatement of the name or title.

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?

An output schema exists, so return shape needn't be explained, and the description covers the two genuinely tricky parts: ambiguous title resolution and the between-seasons miss. It is slightly incomplete only in not saying what happens on a failed title match, which is the scenario it already flags as risky.

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 the id and title paths, the timezone format, and the default are already fully documented in the schema. The description adds a little meaning about title resolution strictness, but the baseline 3 applies when the schema already does the heavy lifting.

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: "Report when a show's next episode airs, converted to a viewer timezone." It is clearly distinguishable from siblings — tvmaze_get_episodes (episode listing) and tvmaze_search_shows (search) — because the description explicitly frames this as a single next-airing lookup with timezone conversion.

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 gives real routing guidance: identify by id or title, and notes the title path uses "a stricter single-match search than tvmaze_search_shows uses," which tells the agent the two tools differ in matching strictness and implies when to prefer one. It stops short of an explicit "use tvmaze_search_shows first when the title is ambiguous" instruction in the prose, though the input schema does carry that.

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.