Skip to main content
Glama
AmoDataBase

amodb-mcp

Official
by AmoDataBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get TV show details

get_tv_show
Read-onlyIdempotent

Fetch a TV show's full record by numeric id—overview, genres, networks, seasons—and append credits, ratings, videos, or streaming providers in one call.

Instructions

Get the full record of one TV show by its numeric id: name, overview, genres, networks, status, number of seasons and episodes, and the list of seasons. Use append to add related data in the same call: credits for cast and crew, videos for trailers, content_ratings for age ratings, watch/providers for where to stream, external_ids for the IMDb, TVDB and Kinopoisk ids, keywords, recommendations, similar, alternative_titles and episode_groups. The reviews section and created_by are empty for most shows. The amodb extras moods, soundtracks, ratings and wikidata are also appended, with the same shapes as for movies. For cinema times use get_showtimes. Use get_season to list the episodes of one season. Get the id from search_titles first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric TV show id, for example 1399. Find it with search_titles.
appendNoExtra data to fetch in the same call, as a list. Allowed values: credits, images, videos, keywords, recommendations, similar, reviews, content_ratings, external_ids, watch/providers, alternative_titles, episode_groups, moods, soundtracks, ratings, wikidata. Example: ["credits", "content_ratings"]. Each value makes the response larger, so request only what you need.
languageNoLanguage tag for titles and overviews, for example en-US, ru-RU or pt-BR. Served languages: en, ru, uk, be, zh, pt, bg, he, cs, ro, fr, pl, it, es. Any other tag falls back to English. Omit to use the server default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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, non-destructive and open-world behavior, so safety is covered. The description adds genuinely useful context beyond that: that 'append' inflates the response and should be requested sparingly, and that certain sections are empty for most shows.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and return shape are front-loaded, followed by append semantics and routing. It is long but nearly every clause carries information; the only mild waste is enumerating append values that the schema also lists.

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?

With no output schema, the description carries the burden of explaining return values, and it does so thoroughly (field list, empty sections, appended extras). Nothing an agent needs to call this correctly appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description explains what each append value actually returns (credits for cast/crew, external_ids for IMDb/TVDB/Kinopoisk ids, etc.) and notes moods/soundtracks/ratings/wikidata mirror the movie shapes — meaning the schema alone does not provide.

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 names a specific verb and resource ('Get the full record of one TV show by its numeric id') and immediately enumerates the returned fields, so it is unmistakably distinct from get_movie, get_season and get_showtimes.

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 explicitly routes the agent to siblings under stated conditions: get_showtimes for cinema times, get_season for the episodes of one season, and search_titles to obtain the id. It also tells the agent which sections are usually empty (reviews, created_by), which prevents wasted calls.

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

Deploy Server

Other Tools