Skip to main content
Glama
paramount-engineering

Roku Dev Studio MCP Server

by paramount-engineering
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Deep-Link into an App

deep_link

Launch a Roku app straight to a specific piece of content (contentId + mediaType) with optional extra parameters via ECP deep-link.

Instructions

Launch an app straight into a specific piece of content via ECP Deep-Link (contentId + mediaType, plus any extra params the channel expects). Equivalent to /launch/?contentId=...&mediaType=...&. Changes device state (foregrounds the app on the requested content). Use this when you have a content id to open; to just open an app to its home screen use launch_app instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesChannel id to launch (e.g. "837" for YouTube, "dev" for the sideloaded Dev App). Discover ids with ecp_query "/query/apps".
deviceNoTarget device — IP (e.g. "192.168.1.137") or serial (e.g. "X0004EX9Q7M"). Omit to use the focused device.
paramsNoExtra key/value query params beyond contentId/mediaType, for channels that expect additional launch args (e.g. { "season": "2" }).
contentIdNoApp-specific content identifier to deep-link to (the value the channel expects for this title/episode). Omit for a plain launch.
mediaTypeNoContent kind, e.g. "movie", "episode", "series", "season", "short-form".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • changedInput schema / properties / device / description
      Previous value: -"Target device — IP (e.g. \"192.168.1.154\") or serial (e.g. \"X00046N6S6F\"). Omit to use the focused device."New value: +"Target device — IP (e.g. \"192.168.1.137\") or serial (e.g. \"X0004EX9Q7M\"). Omit to use the focused device."
  2. Changed4 schema fields changedv1.0.2
    • addedInput schema / properties / appId / description
      Added value: +"Channel id to launch (e.g. \"837\" for YouTube, \"dev\" for the sideloaded Dev App). Discover ids with ecp_query \"/query/apps\"."
    • addedInput schema / properties / contentId / description
      Added value: +"App-specific content identifier to deep-link to (the value the channel expects for this title/episode). Omit for a plain launch."
    • changedInput schema / properties / mediaType / description
      Previous value: -"e.g. \"movie\", \"episode\", \"series\"."New value: +"Content kind, e.g. \"movie\", \"episode\", \"series\", \"season\", \"short-form\"."
    • addedInput schema / properties / params
      Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "Extra key/value query params beyond contentId/mediaType, for channels that expect additional launch args (e.g. { \"season\": \"2\" }).",
+  "type": "object"
+}
  3. First observedv1.0.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the mutation/side-effect profile is partially covered. The description adds valuable behavioral context beyond annotations: 'Changes device state (foregrounds the app on the requested content)' and notes that extra params are passed through to the channel. It doesn't detail failure modes or permission requirements, but the state-change disclosure is meaningful.

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?

Three sentences, all information-dense: the core action, the URL equivalence, the state-change warning, and the routing to the sibling. No filler or repetition of schema details.

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 5-param tool with no output schema, the description covers the core semantics, the state-change side effect, and the sibling distinction. It doesn't explain what the response looks like or what happens on failure, but the URL equivalence and param guidance give an agent enough to construct a correct call. The openWorldHint annotation also signals that extra params are allowed, which the description reinforces.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds value by explaining the relationship between contentId/mediaType and the URL equivalent ('Equivalent to /launch/<appId>?contentId=...&mediaType=...&<extra params>'), and by clarifying that params are channel-specific extras. This goes beyond the schema's individual 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 states a specific verb ('Launch an app straight into a specific piece of content'), names the mechanism (ECP Deep-Link with contentId + mediaType), and explicitly contrasts with the sibling launch_app ('to just open an app to its home screen use launch_app instead'). This clearly distinguishes it from the most similar sibling.

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?

The description gives explicit when-to-use guidance: 'Use this when you have a content id to open; to just open an app to its home screen use launch_app instead.' It also mentions the alternative tool by name, which is exactly what an agent needs to select between the two.

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

Deploy Server

Other Tools