Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425

ncloud_livestation_create_channel

Create a Live Station channel for live streaming with configurable CDN, DVR, encoding, and recording. Use dryRun=true to validate settings without creating.

Instructions

Create a new Live Station channel for live streaming. Use dryRun=true to preview without creating.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNoIf true, returns a preview without actually creating the channel
useDvrYesTime machine (DVR) setting: true to enable rewind
envTypeNoChannel environment typeREAL
cdnDomainNoExisting Global Edge domain (required when createCdn=false)
createCdnYesWhether to create a new CDN (true) or use existing (false)
recordTypeNoRecording storage typeNO_RECORD
channelNameYesChannel name (3-20 chars, Korean/English/numbers/_)
cdnProfileIdYesGlobal Edge profile ID
drmEnabledYnNoWhether to enable Multi DRM
qualitySetIdYesImage quality setting ID (from quality settings list)
recordFormatNoRecording file format (required if recordType=AUTO_UPLOAD)
cdnInstanceNoNoExisting Global Edge instance ID (required when createCdn=false)
cdnRegionTypeNoCDN service region (required when createCdn=true)
immediateOnAirNoAuto-recording on stream start
outputProtocolNoOutput protocol: HLS, LL_HLS (low-latency), or HLS,DASH (both)HLS
recordFilePathNoRecording storage path (required if recordType=AUTO_UPLOAD)
timemachineMinNoTime machine allowance in minutes (360, required if useDvr=true)
isStreamFailOverNoWhether to enable streaming redundancy
recordBucketNameNoRecording storage bucket (required if recordType=AUTO_UPLOAD)
Behavior3/5

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

The description does not contradict the annotations (destructiveHint=false). It adds the dryRun preview behavior but does not disclose other behavioral traits such as cost implications, irreversibility, or authentication needs. For a creation tool, more transparency would be beneficial.

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 extremely concise: two sentences with no fluff. The main action is front-loaded, and the dryRun tip is directly useful. Every sentence earns its place.

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

Completeness2/5

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

With 19 parameters, no output schema, and minimal annotations, the description is too brief. It fails to explain parameter relationships (e.g., conditional requirements for CDN and DRM settings) or provide guidance on common usage patterns. The agent would lack critical context for correct invocation.

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?

Schema description coverage is 100%, so the schema already documents all parameters. The description adds no additional parameter meaning beyond what's in the schema, earning a baseline score of 3.

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 uses specific verb 'Create' and resource 'Live Station channel' with context 'for live streaming'. It also mentions dryRun for preview, making the tool's purpose unambiguous and distinct from siblings like list, get, update, and delete.

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?

The description provides a helpful tip about using dryRun for preview, but lacks explicit guidance on when to use this tool versus alternatives (e.g., update_channel) or when not to use it. No comparative or contextual usage instructions are given.

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/sjk4425/ncloud-mcp-server'

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