Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425

ncloud_livestation_create_vod_channel

Create a Live Station VOD-to-Live channel with Global Edge CDN: specify a profile, quality set, and either create a new CDN or reuse an existing one; preview with dryRun.

Instructions

Create a Live Station VOD-to-Live channel (vodchannelcreate). CDN is Global Edge — give profileId, and either createCdn=true with regionType or createCdn=false with cdnDomain + cdnInstanceNo. Use dryRun=true to preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNoIf true, returns a preview without creating
cdnTypeNoCDN type (Public zone: GLOBAL_EDGE)GLOBAL_EDGE
envTypeNoChannel environment type (default REAL)
cdnDomainNoExisting CDN domain (required when createCdn=false in the Public zone; see ncloud_edge_list_edges)
createCdnYestrue to create a new CDN, false to use an existing one
drmSiteIdNoMulti DRM site ID (required when drmEnabledYn=true; see ncloud_drm_list_sites)
profileIdNoGlobal Edge profile ID (required; see ncloud_edge_list_profiles)
regionTypeNoGlobal Edge service region (required when createCdn=true in the Public zone)
channelNameYesChannel name (3-20 chars: Korean, letters, digits, '_')
drmContentIdNoMulti DRM content ID (3-100 chars: letters, digits, '-', '_'; required when drmEnabledYn=true)
drmEnabledYnNoEnable Multi DRM (Public zone; required there — defaults to false)
qualitySetIdYesQuality set ID (see ncloud_livestation_list_quality_settings; pick a Low Latency set for LL_HLS)
cdnInstanceNoNoExisting CDN instance number (required when createCdn=false)
outputProtocolNoOutput protocol (default HLS)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.1

TDQS

A4.1/5.0
Behavior3/5

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

Annotations only declare destructiveHint=false, so the description must carry most behavioral load. It usefully discloses the dryRun preview and the mutually exclusive CDN configuration branches, but says nothing about permissions, side effects on related resources, or idempotency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences, front-loaded with the action and followed immediately by the CDN configuration rule and the preview option. No filler, though the parenthetical API name is slightly redundant.

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 14-parameter mutation with no output schema, the description captures the critical decision branches (CDN creation mode, dryRun). It omits return values and permission requirements, but the rich 100%-covered schema fills most gaps.

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 coverage is 100%, so baseline is 3. The description adds genuine cross-parameter semantics not expressible in the flat schema: the createCdn branch determines whether regionType or cdnDomain+cdnInstanceNo are needed, and profileId is required.

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 a specific verb and resource ('Create a Live Station VOD-to-Live channel') and even includes the API operation name (vodchannelcreate). It is clearly distinguishable from sibling ncloud_livestation_create_channel (live channel) and ncloud_vodstation_create_channel.

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?

Gives concrete conditional guidance: when createCdn=true supply regionType, when false supply cdnDomain + cdnInstanceNo, and dryRun=true to preview. It does not explicitly name sibling alternatives (e.g. create_channel vs create_vod_channel), but the context is clear enough to route correctly.

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