Skip to main content
Glama
telewebion-mcp

telewebion-mcp

by sepehr071

Telewebion episode

tv_episode
Read-onlyIdempotent

Retrieve details for a Telewebion TV episode by episode ID, including title, program, channel, Tehran air time, duration, quality variants, and watch page URL.

Instructions

Show one episode: title, program, channel, air time (Tehran), duration, quality variants and page URL.

Stream and download tokens are not returned; open url to watch.

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": {
      "episode_id": "<episode_id>"
    },
    "name": "tv_episode"
  }
}

Input Schema

NameRequiredDescriptionDefault
episode_idYesEpisodeID, e.g. 0x12de42a9

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's job is to add context — and it does: air times are Tehran-local, and stream/download tokens are deliberately withheld with the workaround of opening the page URL. That is a genuine behavioral constraint an agent would otherwise discover only by failing. It stops short of describing error behavior for an unknown episode_id.

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?

Two sentences, no filler, and the return-field inventory is front-loaded before the caveat about tokens. Every clause earns its place and nothing is repeated from the schema.

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?

For a one-parameter read-only lookup with no output schema, the description effectively substitutes for one by listing the returned fields, and it discloses the token limitation. The only gap is what happens on an invalid or missing episode_id.

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?

There is a single parameter with 100% schema description coverage, including an example EpisodeID format (0x12de42a9), so the schema already carries the semantics. The description adds nothing about episode_id, which is acceptable at this coverage level but is the baseline rather than added value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a concrete verb+resource ("Show one episode") and enumerates exactly what comes back: title, program, channel, air time, duration, quality variants, page URL. That is far more specific than a restatement of the name. It never names or contrasts a sibling such as tv_program, so the agent must infer the episode-vs-program boundary from the field list alone.

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?

Usage is implied rather than stated: the required episode_id plus "Show one episode" signals a single-item lookup, and "open `url` to watch" hints at the follow-up action. There is no explicit when-to-use/when-not guidance and no pointer to tv_program or tv_search for the cases where the caller lacks an episode ID.

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