Skip to main content
Glama

tv_next

Play the next episode from watch history. Continue Netflix shows or resume recent content on your smart TV without manual browsing.

Instructions

Play the next episode. Continues from watch history.

Args: query: Show name. Omit to continue the most recent Netflix show. tv_name: Target TV name. Omit for default TV.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
tv_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Discloses watch history continuation behavior and Netflix-specific defaulting, but omits error handling (what if no next episode?) and side effects beyond what annotations would provide (none exist).

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?

Extremely concise with front-loaded action statement; Args section is structured and every line provides necessary constraint or default information.

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?

Adequately covers the simple 'next episode' use case given output schema exists; parameter defaults are explained, though edge cases (series completion, offline TV) are unmentioned.

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

Parameters4/5

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

Effectively compensates for 0% schema description coverage by defining 'Show name' and 'Target TV name' semantics, plus default behaviors when parameters are null.

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 specific action (play next episode) and distinguishes from generic playback via 'Continues from watch history', though could clarify distinction from tv_play more 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?

Provides clear parameter omission guidance ('Omit to continue...', 'Omit for default TV') but lacks explicit when-to-use guidance versus sibling tools like tv_play or tv_launch.

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

Install Server

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/Hybirdss/smartest-tv'

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