tv_launch

Launch apps on smart TVs using exact content IDs for deep linking. Open Netflix, YouTube, or Spotify directly to specific content on LG, Samsung, Android TV, and Roku devices.

Instructions

Launch an app, optionally with a deep link.

Use tv_play instead if you have a content name (not ID). Use this when you already have the exact content ID.

Args: app: App name (netflix, youtube, spotify) or raw app ID. content_id: Platform-specific content ID for deep linking. tv_name: Target TV name. Omit for default TV.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`app`	Yes
`content_id`	No
`tv_name`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Tool Definition Quality

A4.5/5.0

Behavior3/5

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

Mentions deep linking capability but lacks disclosure of side effects (e.g., power state changes, app switching behavior) given no annotations 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?

Front-loaded with purpose, followed by usage guidelines and structured Args section; no redundant 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?

Complete for input usage and sibling differentiation; omits behavioral edge cases but output schema exists to cover return values.

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?

Fully compensates for 0% schema description coverage by documenting all three parameters with clear semantics and examples (netflix, youtube, spotify).

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?

States specific action ('Launch an app') and explicitly distinguishes from sibling tv_play by contrasting content ID vs content name usage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when/when-not guidance ('Use tv_play instead if you have a content name... Use this when you already have the exact content ID').

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

Install Server

Smartest-TV

tv_launch

Instructions

Input Schema

Output Schema

Tool Definition Quality

Other Tools

Latest Blog Posts

MCP directory API