Skip to main content
Glama

Example prompts for a template's scene

get_example_prompts
Read-onlyIdempotent

Example text prompts that describe one template's scene, for any image-to-video tool, with the cast's names filled in, plus prompt tips. Give names to put people in by name instead of 'the person in photo 1'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "template": "<template>"
    },
    "name": "get_example_prompts"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesNonames for the people in photo 1, photo 2 …, in order
templateYesThe template, by its name or address name: tiny-desk, iphone-kupi-dance, gangnam-style-dance, bby-wow-dance, bad-times, bad-times-pet, stadium-entrance, rumpelstiltskin, burning-bridges, neon-dance, abcdefg-i-need-money, money-spread, toosie-slide, no-scrubs, you-tweaking-do-a-360, hotel-lobby, my-ride-is-here, ghostface, smalltown-boy, crazy-frog, zombie-couple, storm-dance, alors-on-danse, apt, topo-gigio, closed-on-sunday

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / template / description
      Previous value: -"The template, by its name or address name: bad-times, bad-times-pet, rumpelstiltskin, burning-bridges, neon-dance, abcdefg-i-need-money, tiny-desk, money-spread, toosie-slide, no-scrubs, you-tweaking-do-a-360, hotel-lobby, my-ride-is-here, ghostface, bby-wow-dance, smalltown-boy, crazy-frog, zombie-couple, storm-dance, alors-on-danse, apt, topo-gigio, closed-on-sunday"New value: +"The template, by its name or address name: tiny-desk, iphone-kupi-dance, gangnam-style-dance, bby-wow-dance, bad-times, bad-times-pet, stadium-entrance, rumpelstiltskin, burning-bridges, neon-dance, abcdefg-i-need-money, money-spread, toosie-slide, no-scrubs, you-tweaking-do-a-360, hotel-lobby, my-ride-is-here, ghostface, smalltown-boy, crazy-frog, zombie-couple, storm-dance, alors-on-danse, apt, topo-gigio, closed-on-sunday"
  2. Changed1 schema field changed
    • changedInput schema / properties / template / description
      Previous value: -"The template, by its name or address name: bad-times, rumpelstiltskin, burning-bridges, neon-dance, abcdefg-i-need-money, hotel-lobby, my-ride-is-here, ghostface, bby-wow-dance, smalltown-boy, crazy-frog, zombie-couple, storm-dance, alors-on-danse, apt, topo-gigio, closed-on-sunday"New value: +"The template, by its name or address name: bad-times, bad-times-pet, rumpelstiltskin, burning-bridges, neon-dance, abcdefg-i-need-money, tiny-desk, money-spread, toosie-slide, no-scrubs, you-tweaking-do-a-360, hotel-lobby, my-ride-is-here, ghostface, bby-wow-dance, smalltown-boy, crazy-frog, zombie-couple, storm-dance, alors-on-danse, apt, topo-gigio, closed-on-sunday"
  3. Changed1 schema field changed
    • changedInput schema / properties / template / description
      Previous value: -"The template, by its name or address name: bad-times, rumpelstiltskin, burning-bridges, hotel-lobby, my-ride-is-here, ghostface, bby-wow-dance, smalltown-boy, crazy-frog, zombie-couple, storm-dance, alors-on-danse, apt, topo-gigio, closed-on-sunday"New value: +"The template, by its name or address name: bad-times, rumpelstiltskin, burning-bridges, neon-dance, abcdefg-i-need-money, hotel-lobby, my-ride-is-here, ghostface, bby-wow-dance, smalltown-boy, crazy-frog, zombie-couple, storm-dance, alors-on-danse, apt, topo-gigio, closed-on-sunday"
  4. Changed1 schema field changed
    • changedInput schema / properties / template / description
      Previous value: -"The template, by its name or address name: bad-times, rumpelstiltskin, hotel-lobby, my-ride-is-here, ghostface, bby-wow-dance, smalltown-boy, crazy-frog, zombie-couple, storm-dance, alors-on-danse, apt, topo-gigio, closed-on-sunday"New value: +"The template, by its name or address name: bad-times, rumpelstiltskin, burning-bridges, hotel-lobby, my-ride-is-here, ghostface, bby-wow-dance, smalltown-boy, crazy-frog, zombie-couple, storm-dance, alors-on-danse, apt, topo-gigio, closed-on-sunday"
  5. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare this is a read-only, idempotent, non-destructive operation. The description adds useful context about the returned content (example prompts and prompt tips) and name substitution, but it does not describe output structure, error behavior, or limits.

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 and front-loads the tool's purpose. The second sentence is useful but slightly cumbersome; overall there is little wasted wording.

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 simple two-parameter read-only retrieval tool, the description adequately explains what is returned and how names are used. It could do more to describe the output format or prompt tips, but with annotations and full schema coverage this is reasonably complete.

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 the baseline is 3, but the description adds meaning beyond the schema by explaining that names let users refer to people by name instead of 'the person in photo 1'. It also frames the template parameter as selecting one template's scene.

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 resource: example text prompts for one template's scene, plus prompt tips. It is clear what the tool returns, but it does not explicitly distinguish itself from siblings such as how_to_make or list_templates.

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?

Usage is implied: use this when you need example prompts for a template, and the description explains how names affect the output. However, it gives no explicit when/when-not guidance or alternatives versus sibling tools.

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