Skip to main content
Glama

create_live_asset

A live asset refers to media content/video that is live-streamed through Gumlet. This endpoint creates a live streaming asset allowing users to live stream a video that will be pushed to Gumlet.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_live_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoYour live stream asset title
start_atNo
mp4_accessNoCreates <code>MP4</code> version for download purpose.
resolutionNoRequired resolutions in HLS delivery format for live stream. Can be an array of string out of the following values: `240p`, `360p`, `480p`, `540p`, `720p`, and `1080p`. Resized rendition will retain the input aspect ratio.
orientationNo
live_source_idNoGumlet live video source/collection id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / orientation / enum
      Previous value: -[
      -  "landscape",
      -  "potrait"
      -]New value: +[
      +  "landscape",
      +  "portrait"
      +]
  2. First observed

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare a write operation with readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds that the asset is live-streamed and pushed to Gumlet, but it does not disclose initial asset state, permissions/auth needs, or what happens if creation is repeated. The added behavioral context is limited but consistent with the annotations.

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?

The description is two sentences, front-loading the definition and then the action, with no wasted wording. There is minor redundancy in restating live streaming twice, but the structure is clear and efficient.

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 output schema covers return values and the annotations cover safety semantics, reducing the description's burden. However, for a create tool with six optional parameters and a live workflow involving start_live and complete_live_stream, the description does not explain post-creation steps or required context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description mentions no parameters at all. The schema documents 4 of 6 parameters, but start_at and orientation lack schema descriptions, and the description does not compensate for those gaps at 67% coverage.

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 a specific verb, 'creates', and a specific resource, 'live streaming asset', and it defines what a live asset is. It does not explicitly distinguish this tool from siblings such as create_asset or start_live, so it falls short of a 5.

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?

There is no when-to-use or when-not-to-use guidance. The description does not explain how this differs from create_asset, start_live, or complete_live_stream, nor does it mention prerequisites such as live_source_id or setup steps.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources