Skip to main content
Glama

Export starter code

export_recipe
Read-onlyIdempotent

Generate editable starter source from an adapted recipe, or a reference plus mandatory replacement text: Remotion TSX, HyperFrames HTML, CSS, GSAP, lottie-web JSON or After Effects JSX importer. Optional style sets the background, text colour and font family (your own brand, or values read from get_brand_kit for study); the response reports their contrast ratio. No source footage/logos; unknowns stay adjustable. Generated code is not automatically render-tested.

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": {
      "target": "<target>"
    },
    "name": "export_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNo
textsNo
aspectNo
recipeNo
targetYes
scene_idNo
duration_msNo

Output Schema

NameRequiredDescriptionDefault
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / style
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "background": {
      +      "pattern": "^#[\\da-fA-F]{6}$",
      +      "type": "string"
      +    },
      +    "font_family": {
      +      "pattern": "^[\\p{L}\\p{N} ,'-]{1,100}$",
      +      "type": "string"
      +    },
      +    "foreground": {
      +      "pattern": "^#[\\da-fA-F]{6}$",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the description's job is to add context, and it does: the response reports a contrast ratio, generated code excludes source footage and logos, unknowns remain adjustable, and output is not automatically render-tested. That last caveat is genuinely useful behavioural disclosure an agent could not infer from structured fields, though pagination/size limits and determinism of output are not discussed.

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 dense sentences that front-load the verb and the deliverables before moving to style semantics and caveats, with no filler. The phrasing 'or a reference plus mandatory replacement text' is slightly compressed and takes a second read, but nothing is redundant enough to cut.

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?

An output schema exists so return values need not be explained, and the caveats about footage and render-testing set expectations well. However, for a tool with 7 parameters, a 0%-documented nested recipe schema and enum-driven target/aspect choices, the description leaves too much of the input contract unaddressed to be considered fully complete.

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 0% across 7 parameters including a deeply nested recipe object, so the description must carry the burden and it only partly does. It clarifies target values implicitly (the six formats), explains style sub-fields (background, text colour, font family) and what texts means ('mandatory replacement text'), but says nothing about scene_id, aspect, duration_ms, or the recipe's required reconciliations.

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?

States a concrete verb and output ('Generate editable starter source') and enumerates the exact deliverables: Remotion TSX, HyperFrames HTML, CSS, GSAP, lottie-web JSON, After Effects JSX. It also names the input basis (an adapted recipe, or a reference plus mandatory replacement text), which no sibling such as adapt_scene or plan_structure covers.

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?

Preconditions are implied rather than stated as routing rules: the agent must already have an adapted recipe or a reference plus replacement text, and get_brand_kit is mentioned only as a source of study values. There is no explicit statement of when to choose this tool over adapt_scene, storyboard, or transitions_after, and no when-not guidance.

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