Skip to main content
Glama
Sign In
VideoGen MCP

VideoGen MCP

Official
by video-gen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List languages

list_languages
Read-only

Retrieve supported languages for narration and captions, optionally filtering by a case-insensitive query.

Instructions

List supported languages for narration and captions.

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": "list_languages"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional case-insensitive substring filter across each item's searchable text fields.

Output Schema

NameRequiredDescriptionDefault
languagesYesSupported languages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only that the result is the set of supported languages, which is thin context beyond the name; it says nothing about caching, stability, or auth.

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?

A single short sentence with the resource and its scope front-loaded. Every word earns its place and there is no filler.

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?

With an output schema present, return values need not be explained, and there are no required parameters. Combined with the annotations, everything needed to call the tool correctly is available; only the absence of sibling disambiguation keeps it from a 5.

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% for the single optional 'query' parameter, which is documented as a case-insensitive substring filter. The description adds no additional meaning about the filter, so the schema-describes-everything baseline of 3 applies.

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?

States a specific verb and resource ('List supported languages') and adds scope ('for narration and captions'), which tells the agent exactly what the enumeration covers. It does not, however, differentiate itself from the nearby sibling list_tts_voices, which an agent could plausibly confuse it with.

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 phrase 'for narration and captions' implies the usage context, so an agent can infer this is a lookup for valid language codes. There is no explicit when-to-use statement, no mention of the alternative list_tts_voices, and no exclusion conditions.

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