Skip to main content
Glama

Motion Fab Library

Search recipes

search_recipes
Read-only

Motion Fab's published community recipes: short videos people made, each with the prompt that makes one like it. Without query the newest first; with it, recipes whose English title or prompt has those words. Each has its id, slug, title, one-sentence summary, the Motion Fab template it was made with, tags, the AI model, its page on motionfab.app, its video and how often it was used. The prompt and the techniques come with get_recipe.

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

Input Schema

NameRequiredDescriptionDefault
tagNo
langNoThe language of titles and summaries; default en.
limitNoDefault 10.
queryNoEnglish words, such as "neon logo reveal".
templateNoA Motion Fab template id, such as simple-motion.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a read-only, closed-world operation, so the description only needs to add operational context, which it does: default ordering, the matching rule for `query` (English title or prompt words), and an enumeration of returned fields including template, tags, model, page URL, video, and usage count. It does not discuss pagination beyond `limit` or result totals, which is a minor gap for a search tool.

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 front-loaded with the resource definition and the query/no-query behavior before the field enumeration. The list of returned attributes is somewhat dense, but each item tells the agent what it will get, so little is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 compensates by enumerating the returned fields, and it covers ordering, matching semantics, and where the deeper payload lives (get_recipe). That is enough for an agent to call this correctly without additional documentation.

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 already 80%, so the schema carries most parameter meaning. The description still adds value by explaining what `query` actually matches against (English title or prompt) and what happens when it is omitted (newest first), which the schema does not state.

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 the resource precisely (Motion Fab's published community recipes: short videos with their generating prompt) and describes the operation behaviorally: newest-first without a query, word-match on English title or prompt with one. It also explicitly separates this tool from get_recipe, which carries the prompt and techniques, so an agent can distinguish it from siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context by explaining the two modes (browse newest-first vs. keyword search) and routes the agent to get_recipe when the full prompt or techniques are needed. It stops short of explicit when-not guidance against the other siblings (search_techniques/get_technique), but the recipe-vs-technique distinction is implied by the resource framing.

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