Skip to main content
Glama

tabii_search_content

Search tabii’s catalog by original Turkish title to find matching shows and retrieve IDs, localized titles, types, years, and tabii.com URLs.

Instructions

Search tabii's catalog by (original Turkish) title. query: a title or part of it, e.g. "gassal", "mevlana", "hobbit". language: "tr" (default), "en", "es", "ar" or "ur" — the returned titles are localized to it. limit 1..10 (default 5). Returns id, slug, localized title, original title, type, year and tabii.com URL per match. Note: matching is against the original Turkish title/slug (the site's own search needs a login) and covers the 1,306 titles in the site's sitemaps — some licensed titles (e.g. The Hobbit) are absent from the sitemaps and cannot be found this way; they are reachable by id via tabii_homepage's featured sections. English titles are shown on the matches but cannot be searched.

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": {
      "query": "<query>"
    },
    "name": "tabii_search_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
languageNotr

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full load and does so: it discloses the matching basis (original Turkish title/slug, not localized titles), the corpus size and its source (sitemaps), known coverage gaps for licensed titles, and the fact that localized English titles are displayed but not searchable. These are exactly the constraints an agent needs to avoid false-negative conclusions.

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?

Purpose and parameters are front-loaded and each sentence carries real information. The one redundancy is the return-field list (id, slug, titles, type, year, URL), which duplicates the existing output schema, and the parenthetical caveats make the text denser than necessary.

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?

For a three-parameter search tool with an output schema, no annotations, and no nested objects, the description covers semantics, localization behavior, corpus coverage, and the fallback path for unfindable titles. Nothing an agent needs to call it correctly is missing.

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

Parameters5/5

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

Schema description coverage is 0%, yet all three parameters are explained in prose: query is a title or partial title with examples, language enumerates tr/en/es/ar/ur and states its effect on returned titles, and limit is bounded 1..10 with a default of 5. This fully compensates for the empty schema descriptions.

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 opens with a specific verb and resource: search tabii's catalog by original Turkish title. It also scopes the corpus (1,306 sitemap titles) and implicitly separates itself from tabii_get_show (id-based) and tabii_homepage (featured sections), so an agent can pick the right tool without opening a schema.

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 clear usage context: search works on the original Turkish title/slug, the site's own search requires login, and titles missing from sitemaps (e.g. The Hobbit) must be reached by id through tabii_homepage's featured sections. The only gap is that it never explicitly says to prefer tabii_get_show when an id is already known, so routing in that case is inferred rather than stated.

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