Tvmaze

List Episodes

list_episodes

Read-onlyIdempotent

List all episodes of a show. Returns season, number, name, airdate, runtime, and summary.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`show_id`	Yes	TVMaze show ID
`specials`	No	Include special episodes (default false)

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes	Total episode count
`show_id`	Yes	TVMaze show ID
`episodes`	Yes	List of episodes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "show_id": 1
+  },
+  {
+    "show_id": 139,
+    "specials": true
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Total episode count",
+      "type": "number"
+    },
+    "episodes": {
+      "description": "List of episodes",
+      "items": {
+        "properties": {
+          "airdate": {
+            "description": "Air date (YYYY-MM-DD)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "airtime": {
+            "description": "Air time (HH:MM)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "TVMaze episode ID",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Episode title",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "number": {
+            "description": "Episode number in season",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "rating": {
+            "description": "Episode rating",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "runtime_min": {
+            "description": "Episode runtime in minutes",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "season": {
+            "description": "Season number",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "summary": {
+            "description": "HTML-stripped episode summary",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "tvmaze_url": {
+            "description": "Episode page URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "type": {
+            "description": "Episode type",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "show_id": {
+      "description": "TVMaze show ID",
+      "type": "number"
+    }
+  },
+  "required": [
+    "show_id",
+    "count",
+    "episodes"
+  ],
+  "type": "object"
+}

First observedMay 12, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the safety profile is clear. The description adds return field details but no additional behavioral traits (e.g., pagination, ordering).

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?

Single sentence with key fields listed. No redundant words, front-loaded with main action. Efficient and scannable.

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?

Given low complexity (2 params, simple output), annotations, and existing output schema, the description is complete enough. Minor missing context like typical use case scenarios but not critical.

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%; description adds no extra meaning beyond the schema. Both parameters (show_id, specials) are fully documented in schema with types and example values.

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?

Description clearly states verb 'list', resource 'all episodes of a show', and enumerates returned fields (season, number, name, airdate, runtime, summary). It distinguishes from sibling tools like get_schedule and 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 Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives. While the purpose is clear, the description lacks when-not or context for choosing over siblings like get_show or get_schedule.

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

All Tvmaze tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.