Skip to main content
Glama
telewebion-mcp

telewebion-mcp

by sepehr071

Telewebion program

tv_program
Read-onlyIdempotent

Retrieve a program's summary and its episodes in newest-first order, including episode page URLs and pagination options for browsing.

Instructions

Show a program's summary and its episodes, newest first, with episode page URLs.

Page with offset. Dates are when the episode was published on the site.

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": {
      "program_id": "<program_id>"
    },
    "name": "tv_program"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
program_idYesProgramID from tv_search or an episode, e.g. 0x11e5eaeb

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/openWorld, so the description rightly focuses on other behavior: results are ordered newest first, episodes include page URLs, and dates mean site publication rather than air time. That date disambiguation is genuinely useful context an agent could not infer.

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 short sentences, front-loaded with the return content before the paging note. Every clause carries information, though 'Page with `offset`' is terse enough to be slightly cryptic about the paging unit.

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 sketch the response, and it does: a summary, an episode list, ordering, URLs, and date semantics. It omits whether a total count or end-of-list signal is returned, which matters for paging loops.

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 33%, so the description should carry more weight. It explains offset as a paging mechanism, but says nothing about limit (its default of 12 and cap of 50 are only visible in the schema) and nothing about how offset relates to limit.

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?

States a specific verb and resource: shows a program's summary plus its episodes, with ordering and included fields named. This clearly separates it from tv_episode (single episode) and tv_channel_schedule, though no sibling is named explicitly.

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?

The only usage guidance is 'Page with `offset`', which covers incremental paging but not when to pick this over tv_episode or tv_search. The program_id provenance hint lives in the schema, not the description, so guidance is implied rather than stated.

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