My TV Channel

Create channel

create_channel

Create a 24/7 linear TV channel. It will NOT be live yet — a channel goes live automatically once it has at least 4 ready assets AND at least 15 minutes of total content. is_public lists it in Discover and is available on every subscription tier, including Starter.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Display name
`tags`	No
`handle`	Yes	3-63 chars, lowercase a-z 0-9 and hyphens. Becomes {handle}.my-tv-channel.com
`category`	No
`location`	No	Required only when channel_type is "location"
`is_public`	No	List in Discover. Available on all tiers.
`description`	No
`orientation`	No	vertical = 9:16
`channel_type`	Yes	Use "thematic" unless the channel is tied to a place
`primary_language`	No	ISO 639-1, e.g. "en", "fr"

TDQS

A3.5/5.0

Behavior4/5

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

The description discloses important behavioral traits beyond the annotations: the channel will not be live immediately but automatically goes live after having at least 4 ready assets and 15 minutes of total content. It also explains that is_public affects Discover visibility and tier availability. This provides operational context the annotations do not cover.

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 three sentences with the core purpose front-loaded. Each sentence adds unique value: the action, the activation condition, and the is_public effect. No redundant or filler wording is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description explains the activation mechanism and is_public but omits any mention of the response format (no output schema exists) and does not cover the full parameter set or workflow. Given the tool's complexity (10 parameters, nested objects), the description is helpful but not fully complete for an agent.

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?

With 70% schema coverage, most parameters already have descriptions. The description adds meaning for is_public (Discover listing and tier reach) and the overall live condition, but it does not explain the other seven parameters beyond what the schema provides.

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?

The description states 'Create a 24/7 linear TV channel' with a specific verb and resource, clearly distinguishing it from update_channel and archive_channel. The added detail about the channel not being live yet further clarifies the tool's scope, though it does not explicitly name sibling alternatives.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus update_channel or other channel-management tools. The only usage-related hint is that the channel becomes live after meeting content thresholds, which is a behavioral note rather than a comparative usage guideline.

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

All My TV Channel tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

Most tools are clearly distinct: channel lifecycle (create/get/update/archive/list), asset management (import/delete/list/set_asset_weight), schedule management (get/set/validate/regenerate), and transcode (get status/retry). Minor overlap exists between archive_channel and delete_asset, but descriptions clarify the scope (whole channel vs single video). import_video_from_url and import_youtube_video are distinct in source and ownership requirements.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: archive_channel, create_channel, delete_asset, get_channel, list_assets, set_asset_weight, validate_schedule_rules, etc. Verbs are action-oriented (create, get, list, update, archive, delete, import, set, regenerate, retry) and nouns are resource names (channel, asset, schedule, transcode). No mixed conventions or vague verbs like 'process' or 'do_thing'.

Tool Count5/5

19 tools is well-scoped for a TV channel management server covering channel lifecycle, asset ingestion, scheduling, and transcode monitoring. Each tool addresses a distinct need and the count feels proportional to the complexity of managing a 24/7 linear TV channel. Not bloated with redundant tools, and each has a clear purpose.

Completeness4/5

The surface covers the core domain comprehensively: channel CRUD (create, get, update, archive, list), asset management (import, delete, list, weight), scheduling (set rules, validate, regenerate, get schedule), and transcode monitoring (status, retry). Minor gaps: no direct way to upload local files (stated as a limitation), no channel deletion (only archive), and no ability to manage playlists explicitly. However, these are acknowledged design constraints or edge cases, so the surface is largely complete for the stated purpose.

Resources

Need Help?