Skip to main content
Glama

studio_recipes

Read-onlyIdempotent

List the Studio recipes the organization saved: a named format plus its settings (avatar, voice, text style, captions, aspect, duration, slides, quality, hook rule, chat app, call to action, music, script structure). To make content "the usual way" or with a named recipe, pass its id as recipeId to studio_generate: the recipe's format and settings are used, and anything you pass yourself wins. A recipe never holds the topic, hook words or media: still pass prompt / hook / mediaIds as needed. Free, no credits.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
recipesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/no open-world, so the safety bar is low, and the description still adds cost information ('Free, no credits') plus merge-override semantics that annotations cannot express. The note that a recipe never holds topic/hook/media further discloses behavior beyond structured fields.

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?

Three front-loaded sentences with no filler, and the override rule is stated before the caveats. The 13-item parenthetical settings list is dense and slightly over-enumerated for a read-only listing call, but it does earn its place by showing what a recipe captures.

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?

An output schema exists, so return values need not be described, and the description covers the two things an agent actually needs: what is listed and how the ids get consumed. Nothing required for a correct call is missing.

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?

Zero parameters, so the baseline of 4 applies; the description wisely spends its words on the downstream recipeId contract on studio_generate instead. There is no schema surface left unexplained.

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?

Opens with a specific verb+resource ('List the Studio recipes the organization saved') and enumerates exactly what a recipe contains, so an agent knows the payload shape before calling. It never names studio_formats explicitly, so the boundary between 'recipes' and 'formats' is only implied by 'a named format plus its settings'.

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

Usage Guidelines5/5

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

Gives the forward path explicitly: to make content 'the usual way', pass the id as recipeId to studio_generate, and states the precedence rule ('anything you pass yourself wins'). It also warns what a recipe does NOT cover (topic, hook words, media) and that prompt/hook/mediaIds must still be supplied — a real usage pitfall closed.

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