Skip to main content
Glama
telewebion-mcp

telewebion-mcp

by sepehr071

Telewebion search

tv_search
Read-onlyIdempotent

Search Persian or English TV program, movie, and series titles to retrieve matching Telewebion page URLs and IDs. Use program IDs or product links to open on-demand content.

Instructions

Search programs (TV shows) and movies/series by title, with their page URLs.

Programs have a program_id for tv_program; movies and series are on-demand product pages only.

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": "tv_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesPersian or English title text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the safety profile is covered. The description adds meaningful context beyond them: results carry page URLs, and only program records carry a program_id, which tells the agent what shape of entity it will get back.

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?

Two tight sentences with the core scope front-loaded and no filler. The second sentence is slightly compressed ('Programs have a program_id for tv_program') and could be phrased more plainly, but it earns its space.

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 must convey return content, and it does: page URLs and program_id presence per result type. It omits how many results come back by default and how results are ordered, minor gaps for a simple two-parameter search.

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 50%: query is documented as 'Persian or English title text', but limit has no description. The description reinforces that matching is title-based only (not cast, genre, or description), which is useful, yet it says nothing about how limit affects results or ordering.

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 gives a specific verb and resource ('search programs (TV shows) and movies/series by title') plus a scope boundary: programs return a program_id usable with tv_program, while movies/series exist only as on-demand product pages. That boundary alone lets an agent distinguish this lookup tool from tv_program detail retrieval.

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 implicitly routes the agent: search here first, then use the returned program_id with tv_program for programs, and note that movies/series have no such follow-up. There is no explicit 'when not to use' statement or guidance for title-ambiguous cases, so it falls short of a 5.

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