Skip to main content
Glama

Motion Fab Library

Get a recipe

get_recipe
Read-only

One published recipe whole: its prompt (sections in tags such as and ), what the reader brings (inputs: a video, a logo...), the template and model it was made with, its video, and its techniques (id, name, kind) whose standalone code get_technique gives. Use the prompt as a starting point for a similar video in Motion Fab or with your own tools.

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": {
      "id": "<id>"
    },
    "name": "get_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA recipe id or slug from search_recipes.
langNoThe language of the texts; default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint true, openWorldHint false), so the description's job is to add context, which it does: it discloses that only *published* recipes are returned and details the composition of the payload. It omits failure behavior for an unknown id/slug and whether techniques are truncated, keeping 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, with the content inventory front-loaded after the colon and the practical usage note last. No padding or restated boilerplate.

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 convey the return shape, and it does so in detail (prompt tags, inputs, template/model, video, technique triples). The main remaining gap is the behavior of the `lang` parameter and error cases, which matters moderately for a simple two-parameter read tool.

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%, documenting `id` (recipe id or slug from search_recipes) and `lang` with an enum, so the schema already carries parameter meaning. The description adds nothing about `lang` behavior (e.g., whether untranslated sections fall back to English), which would have been genuinely additive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete resource (a single published recipe) and enumerates its contents: prompt with tagged sections, `inputs`, template, model, video, and techniques. It also routes technique code retrieval to get_technique, so an agent can distinguish it from that sibling without reading either schema.

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 by the phrase 'Use the prompt as a starting point for a similar video in Motion Fab or with your own tools,' which explains what to do with the result. However, it never states when to call this versus search_recipes, nor any prerequisite such as obtaining the id from search_recipes (that only appears in the schema).

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