Skip to main content
Glama

How to make a template's video

how_to_make
Read-onlyIdempotent

How to make one template's meme video on Put Me In, step by step: the photos it needs (one per person, with the role each plays), photo requirements, what you get back, and its page.

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

Input Schema

NameRequiredDescriptionDefault
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.7/5.0
Behavior4/5

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

The annotations already declare this a safe, idempotent, closed-world read, and the description goes beyond them by describing the shape of the answer: the photos needed one per person with each role, photo requirements, what you get back, and the page. It does not state how long or in what format the instructions arrive, which keeps it short of a 5.

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?

It is a single front-loaded sentence with the purpose first and the contents listed after the colon, and no filler. The closing phrase 'and its page' is vague and slightly awkward, which costs it a point.

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?

The one-parameter tool has no output schema, so the description correctly fills that gap by previewing what the answer contains. The only remaining hole is that it never says what happens if the template name is not recognized.

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 coverage is 100%, and the template parameter even carries a full list of accepted names, so the schema already does the heavy lifting. The description adds nothing about resolving a name versus an address name or handling an unknown template, so the baseline 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?

The description states a specific resource and outcome: step-by-step instructions for making one template's meme video, and enumerates what the answer covers (required photos, photo requirements, result, page). That is clear enough for the agent to tell this apart from list_templates or get_faq without opening the schema, though no sibling is named explicitly.

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 only implied: an agent can infer it should call this when it needs to know how to produce a particular template's video. There is no explicit when-not condition and no pointer to alternatives such as list_templates for discovery or get_example_prompts for prompts.

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