Skip to main content
Glama

Generate Scene Frame

generate_scene_frame

Generate one actor-grounded narrative first frame from one to four existing LetMeActForYou actor_ids plus location, wardrobe, pose, and composition. Uses actor headshots as image references and returns a stored image_url. For multi-shot continuity, first generate a wide scene reference, then pass its scene_frame_id as continuity_scene_frame_id while specifying a fresh camera setup in composition and fresh blocking in pose for every shot. Pass only the actor_ids that should be visible in that shot. Pass composition_reference_url to preserve a Blender previs frame's camera and blocking while replacing proxy geometry with actors and the finished set. Defaults to Gemini; pass provider='grok' to use Grok Imagine. Use this before animation when a close-up headshot is not enough.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
moodNoOptional lighting or emotional tone.
poseNoBody pose, blocking, or pre-action moment to capture.
modelNoOptional image model override, e.g. gemini-3.1-flash-image or grok-imagine-image-quality.
locationYesPhysical set or location for the narrative frame.
providerNoImage provider for actor-grounded frame generation. Use 'grok' to route to Grok Imagine; Grok supports up to 3 actor reference images.gemini
wardrobeNoWardrobe direction for the actor(s), if different from their baseline identity.
actor_idsYesOne to four actor ids from casting_roster, my_actors, or create_actor. The generated frame uses their headshots as identity references.
compositionNoCamera framing and layout, e.g. wide two-shot, over-the-shoulder, low angle.
aspect_ratioNoOutput canvas. Use 16:9 for landscape film/TV coverage.9:16
composition_reference_urlNoOptional HTTPS image URL for a previs frame whose camera, blocking, subject scale, screen positions, and visible landmarks should be preserved.
continuity_scene_frame_idNoOptional scene_frame_id owned by the caller to use as a scene-continuity reference. It preserves set topology, fixed furniture, props, lighting motivation, and wardrobe, but pose and composition define a new camera setup and new actor blocking. Pass only the actors visible in this shot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / aspect_ratio
      Added value: +{
      +  "default": "9:16",
      +  "description": "Output canvas. Use 16:9 for landscape film/TV coverage.",
      +  "enum": [
      +    "16:9",
      +    "9:16"
      +  ],
      +  "title": "Aspect Ratio",
      +  "type": "string"
      +}
    • addedInput schema / properties / composition_reference_url
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 500,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Optional HTTPS image URL for a previs frame whose camera, blocking, subject scale, screen positions, and visible landmarks should be preserved.",
      +  "title": "Composition Reference Url"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / continuity_scene_frame_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 80,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Optional scene_frame_id owned by the caller to use as a scene-continuity reference. It preserves set topology, fixed furniture, props, lighting motivation, and wardrobe, but pose and composition define a new camera setup and new actor blocking. Pass only the actors visible in this shot.",
      +  "title": "Continuity Scene Frame Id"
      +}
  3. Added

TDQS

A5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), the description discloses important runtime behaviors: headshots are used as identity references, the output is a stored image_url, default provider is Gemini, Grok caps at 3 actor references, and continuity_scene_frame_id preserves set/props/lighting but NOT pose/composition. No contradiction with annotations.

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?

Six sentences, each earning its place: purpose, continuity workflow, actor filtering, composition reference, provider default, and timing use-case. It is front-loaded and reads naturally without redundancy.

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?

For an 11-parameter tool with no output schema, the description covers the essential operational context: what the tool returns (image_url), how to chain for continuity, how to preserve previs composition, and when to choose providers. The absence of an output schema is mitigated by mentioning the stored image_url return.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds high-value semantics: continuity_scene_frame_id resets pose/composition, composition_reference_url preserves previs camera/blocking, and actor_ids should be limited to visible actors. It clarifies that pose/composition parameters are reused per shot.

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 begins with a specific verb and resource: 'Generate one actor-grounded narrative first frame' from actor_ids plus location, wardrobe, pose, and composition. It also distinguishes itself from adjacent tools by stating 'Use this before animation when a close-up headshot is not enough,' clearly separating it from animation and character-video siblings.

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?

Explicit workflow guidance is provided: 'For multi-shot continuity, first generate a wide scene reference, then pass its scene_frame_id...' and 'Pass only the actor_ids that should be visible in that shot.' It also explains when to use composition_reference_url and recommends provider switching via 'pass provider='grok''. The closing line gives a concrete alternative-use context against existing animation tools.

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.