Skip to main content
Glama

tabii_get_show

Retrieve full details for a tabii title by show ID or slug, including localized titles, seasons and episode lists, cast, genres, audio and subtitle languages, and the tabii.com URL.

Instructions

Full detail of one tabii title. Give show_id (numeric, from tabii_search_content) or slug (e.g. "gassal", "mevlana-celaleddin-i-rumi"). language: "tr" (default), "en", "es", "ar" or "ur". Returns localized title, original title, type, year, genres, age restriction, season count, seasons with episode titles + durations (capped at 60 episodes), cast, directors, writers, description, audio/subtitle languages, badges, trailer count and the tabii.com URL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tabii_get_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNo
show_idNo
languageNotr

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It does disclose meaningful traits — localization by language, the 60-episode cap on season payloads, which fields come back — but it never states what happens when both slug and show_id are omitted, since all three parameters are optional, nor any precedence rule when both are given.

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?

It is front-loaded with the purpose and the identifier guidance, then the language options, with the payload inventory last. The long trailing enumeration of return fields is somewhat wasteful given an output schema already exists, but it reads as one dense, purposeful block with no filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has three optional parameters and no required ones, and the description never closes that gap by saying at least one identifier is needed — an agent could call it with an empty object. Return values are covered by the output schema, making the field list redundant rather than compensatory, so the definition is adequate but leaves a real invocation ambiguity.

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 description coverage is 0%, so the description must compensate, and it largely does: show_id is typed as numeric and tied to its source tool, slug is illustrated with two real examples, and language gets an enumerated set of accepted values with "tr" as default. The only unaddressed semantics are mutual exclusivity/precedence between slug and show_id.

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?

"Full detail of one tabii title" is a specific verb + resource + cardinality, and the description names tabii_search_content as the source of the identifier, which separates it from the sibling search tool. An agent can tell it retrieves a single title's record versus searching or browsing the homepage.

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 explicitly routes the agent: obtain show_id from tabii_search_content, or use a slug like "gassal". That is clear entry-point guidance. What is missing is any statement of when NOT to use it (e.g. vs tabii_homepage or a live-channel tool) and what happens if neither identifier is supplied.

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