Skip to main content
Glama
smeet666

mcp-tvsubtitles

Search television series

search_titles
Read-onlyIdempotent

Search tvsubtitles.net for a TV series by name, filtering by year or media type, and optionally retrieving subtitle, episode, and season counts.

Instructions

Search tvsubtitles.net for a television series by name. The site catalogues television only, so 'media_type' takes 'tv' or 'any' and a film is refused rather than answered with an absence. Each row carries the id the other tools take, the years the site publishes for the show, and the languages it draws a flag for. Pass 'with_counts' for how many subtitles, episodes and seasons the site holds per show: it publishes those three on its catalogue index rather than on the page a search answers with, so reading them costs one further request over a large page, and each counts the whole show. Show ids come from here and are never built by hand.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoKeep only shows whose published years cover this one. When that leaves nothing, the search is reported without it and a note says the year was set aside.
limitNoRows to render, 20 by default and 100 at most.
queryYesThe name of a series, or part of one. The site matches on the name alone.
media_typeNo'tv' or 'any' both search the catalogue, which holds television only. 'movie' is refused, because answering it with an empty list would report an absence this site cannot establish.
with_countsNoRead each row's subtitle, episode and season counts from the site's catalogue index, which costs one further request over a page of several hundred kilobytes. Each figure counts the whole show rather than this search, each is read on its own, and a cell the index leaves empty keeps a null.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesYes
queryYes
cachedYesTrue when the answer was served from memory rather than the site.
sourceYes
resultsYes
counts_scopeYesWhat the three counts count, when they were read: every season of that show together, which is a different figure from the rows this search served. Null when no counts were asked for.
result_countYesRows rendered here.
total_countsYesWhat 'total_available' counted: the rows this one search came back with.
filters_appliedYes
filters_droppedYes
total_availableYesRows the site's answer held, before any were rendered.
Install Server

TDQS

A4.8/5.0
Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: 'movie' is refused rather than answered with an empty list, 'with_counts' triggers an extra large request and counts figures for the whole show, cells can remain null, and site coverage is television-only. It also discloses consequences such as the additional request cost. No contradiction with readOnly/openWorld/idempotent hints.

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?

The description is dense but every sentence adds distinct information: coverage limitation, media_type behavior, row contents, with_counts cost/counting semantics, and ID provenance. It is front-loaded with the core purpose and never repeats the title or schema.

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 search entry-point tool, the description covers what it returns, how parameters change behavior, cost implications, and how the returned IDs connect to other tools. An output schema also exists, so not listing return fields is acceptable; nothing an agent needs before invoking it 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 coverage is 100%, but the description still adds meaning: it explains the 'with_counts' request-cost and whole-show counting semantics, explains why 'movie' is refused despite the enum allowing it, and states that query matches on the name alone. This goes well beyond the field 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 clear verb and resource: 'Search tvsubtitles.net for a television series by name.' It goes beyond the title by describing what each returned row contains and notes it returns the IDs that sibling tools consume, so an agent can distinguish this search tool from the get/list siblings.

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 context for when to call it: this is the source of show IDs for other tools ('Show ids come from here and are never built by hand'), and it states a firm exclusion — films are refused, so the tool should not be used for movie searches. It does not explicitly name sibling alternatives or say 'use list_subtitles instead,' so it stops 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.

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/smeet666/mcp-tvsubtitles'

If you have feedback or need assistance with the MCP directory API, please join our Discord server