Skip to main content
Glama

get_video_generator_url

Retrieve the official URL for a selected AI rap video template or the general rap generator, so you can open the correct generation page.

Instructions

Get the official generator page for a template or the general AI rap generator.

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

Input Schema

NameRequiredDescriptionDefault
slugNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. Beyond the implied read-only nature of "Get," it discloses nothing about the return format, whether the URL is stable or public, whether authentication is required, or what error occurs for an invalid slug. The word "official" hints at a canonical link but is not elaborated.

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?

A single tightly written sentence with no filler, and the two supported modes are front-loaded. It is appropriately sized for a trivial one-parameter lookup tool, though one more clause on the return value would have cost little.

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?

This is a simple tool with one optional enum parameter and no output schema or annotations, so expectations are modest. The description covers both invocation modes but leaves the actual result (a URL string) and its handling implicit, relying on the tool name to fill that gap.

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 0%, and the single parameter is an optional enum of two slugs. The description partially compensates by framing the parameter as selecting a template versus falling back to the general generator, which clarifies the meaning of omission — information not present in the schema. It does not explain the individual slug values or what happens if an unknown value were passed.

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 uses a concrete verb ("Get") and resource ("official generator page") and explicitly covers two modes: a specific template page or the general AI rap generator. It is distinguishable from siblings by focusing on the generator page rather than template metadata or listing. It stops short of stating that the return value is a URL, which the name implies but the text never confirms.

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 "for a template or the general AI rap generator" phrasing implies that supplying a slug targets a template page while omitting it yields the general generator, which is useful routing guidance. However, it never explains when to prefer this over siblings like get_template_info, nor does it state prerequisites or limitations.

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