Skip to main content
Glama
crawde

Vadyu MCP Server

by crawde
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vadyu_list_recipes

Lists Composable Director Recipes with collections, tags, themes, block schemas, audio moods, credit rules, and optional smart recommendations filtered by vertical or credit budget.

Instructions

List all 80+ unified Composable Director Recipes (signature presets plus the Recipe Foundry catalog, each with collection, tags and theme), custom block schemas (ai_scene, text_card, logo_outro, ken_burns_still, flash_cut_intro, cta_endcard, split_before_after), synthesized audio moods (nyc_dusk, luxury_ambient, modern_pulse, none), credit rules, and optional smart recipe recommendations.

Input Schema

NameRequiredDescriptionDefault
verticalNoOptional commercial vertical filter ('horology_watch', 'skincare_beauty', 'fragrance_perfume', 'beverage_culinary', 'fashion_runway', or shorthand 'watch', 'skincare', 'fragrance', 'coffee', 'fashion').
max_creditsNoOptional maximum AI render credits per ad (e.g., 1 or 2) when filtering recommendations.
recommend_forNoOptional product or fashion/portrait description (e.g., 'Tall Swedish blonde supermodel on a golden runway' or 'Matte black chronograph watch'). When provided, returns the top 3 ranked recipe recommendations with pre-filled suggested_payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses the scope of returned data (80+ recipes, block schemas, moods, credit rules), which is useful context, but it does not clarify pagination, response size, permissions, or whether the operation is purely read-only (though 'List' implies it). No contradictions exist.

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 a single dense sentence that is front-loaded with the main action. It is information-rich without filler, though the long enumeration of internal block schema names and audio moods may be more detail than needed for tool selection.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given there is no output schema, the description should fully explain return values; it does enumerate content categories, which helps, but it omits pagination, response format, and how the optional filters and recommendations interact. It is adequate but leaves notable gaps.

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%, so the baseline is 3. The description mentions 'optional smart recipe recommendations' which maps to `recommend_for`, but it adds no syntax, format, or interaction details beyond what the schema already provides for all three parameters.

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 uses a clear verb ('List') and names the resource ('Composable Director Recipes'), and it enumerates the bundled data (signature presets, Recipe Foundry catalog, block schemas, audio moods, credit rules). However, it does not differentiate this tool from siblings like `vadyu_list_sequences_and_formats` or `vadyu_list_videos`, leaving the agent to infer scope.

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 explicit guidance on when to use this tool versus alternatives, no exclusions, and no stated prerequisites. The only conditional hint ('optional smart recipe recommendations') is tied to a parameter, not to tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools