Skip to main content
Glama

Recommended video settings

recommend_settings
Read-onlyIdempotent

Recommended settings for one template: the model, the quality to pick (480p, 720p or 1080p, with prices and what each is good for), the aspect ratio, the length in seconds, sound, and the cast (how many photos and who each person plays).

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

Input Schema

NameRequiredDescriptionDefault
useNowhere the video is going: chat (480p), story (720p) or post (1080p); leave out for the site's recommendation
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and purity are covered without help. The description adds some value by disclosing the shape of the recommendation payload (prices per quality tier, cast composition), but it says nothing about behavior on an unrecognized template name or whether recommendations are static per template.

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 sentence with the core statement front-loaded before the colon-delimited enumeration of what is returned. The list is long but each item carries distinct information; minor redundancy in repeating the resolution tiers that also appear in the schema.

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 no output schema, the description must carry the return-value burden, and it does so by enumerating the recommended fields including casting detail and per-quality pricing. For a read-only two-parameter lookup this is close to sufficient; only the missing when-to-use routing and unknown-template behavior keep 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 coverage is 100%, so both parameters are already documented, including the chat/story/post to resolution mapping and the full template name list. The description's mention of 480p/720p/1080p and prices reinforces the quality tiers but describes returned values rather than adding meaning to the two input parameters, so 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 clearly frames the tool as returning 'Recommended settings for one template' and then enumerates the specific facets covered (model, quality, aspect ratio, length, sound, cast). This is specific about the resource and the content, though it is phrased as a noun list rather than stating a verb like 'returns', and it never names how it differs from list_templates or how_to_make.

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 guidance on when to call this versus the siblings (list_templates, how_to_make, get_example_prompts). The useful rule 'leave out use for the site's recommendation' lives only in the input schema, not the description, and nothing tells the agent whether to call list_templates first to obtain a valid template name.

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