Skip to main content
Glama

Sequencer

by media.sequencer
OverviewDiscussionsAdmin

create_asset

Create a new character, location, prop, or legacy text-only style asset in a workspace. Character, location, and prop prompts generate a reference image. Style assets do not generate images; routine projects should store their global visual style in edit.style instead. existingMediaUrl may attach an explicit user-supplied reference image.

Input Schema

NameRequiredDescriptionDefault
nameYesAsset name
typeYesType of asset to create
editIdNoEdit ID — REQUIRED when creating assets within an edit context. Assets without editId will NOT appear in the editor Assets tab.
promptNoPrompt for generating a character, location, or prop reference image. For a legacy style asset, this is normalized into its text description and no image is generated. Ignored if existingMediaUrl is provided.
modelIdNoModel ID for character, location, or prop image generation. Pass the user's preferred model from MODEL_PREFERENCES if set. Defaults to Nano Banana 2.1 (google-nano-banana-2-1). Ignored for style assets and when existingMediaUrl is provided.
folderIdNoFolder to place the asset in
descriptionNoAsset description. For style assets, this must be one short sentence describing only the visual aesthetic shared by every shot; do not list characters, locations, props, actions, or shot-specific objects.
workspaceIdYesThe workspace ID
existingMediaUrlNoDownload URL of an existing image to use as the asset reference image (e.g. from a user-attached file). When provided, skips image generation and uses this image directly.
voiceDescriptionNoFor character assets: voice/accent/personality description used for speech generation, e.g. "slow casual Gen Z woman, vocal fry, Valley girl / LA accent".
existingMediaFileNameNoOriginal file name for existingMediaUrl. Used when copying the uploaded image into workspace media storage.
existingMediaMimeTypeNoMIME type for existingMediaUrl. Used when copying the uploaded image into workspace media storage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / modelId / description
      Previous value: -"Model ID for character, location, or prop image generation. Pass the user's preferred model from MODEL_PREFERENCES if set. Defaults to Nano Banana Pro (google-gemini-3-image). Ignored for style assets and when existingMediaUrl is provided."New value: +"Model ID for character, location, or prop image generation. Pass the user's preferred model from MODEL_PREFERENCES if set. Defaults to Nano Banana 2.1 (google-nano-banana-2-1). Ignored for style assets and when existingMediaUrl is provided."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries full burden and does disclose key non-obvious behavior: character/location/prop prompts trigger reference-image generation while style assets do not, and existingMediaUrl skips generation. It omits permissions, cost, or failure behavior, but the generation-vs-no-generation distinction is valuable side-effect disclosure.

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 short sentences, front-loaded with the core action and followed by the two behaviorally important qualifications. No filler, though it could be tightened slightly.

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

Completeness4/5

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

For a 12-parameter, no-annotation, no-output-schema tool, the description covers the high-risk behavioral points (image generation, style handling, reference-image attachment). It leaves the editId/edit-context requirement entirely to the schema, which is acceptable given 100% coverage but is a notable structural gap.

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 schema already documents all 12 parameters, making 3 the baseline. The description reinforces existingMediaUrl semantics and the style/prompt interaction, but adds little beyond what the schema already states.

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 specific verb (create) and resource (asset) and enumerates the asset types it handles (character, location, prop, style). This clearly separates it from siblings like update_asset, list_assets, and create_workspace without needing to open any 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?

Provides explicit when-not guidance by steering routine global visual style to edit.style instead of creating a style asset. However, it offers no routing against neighboring creation tools (create_scene, generate_image, import_media_from_url) or conditions for choosing each asset type.

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

All Sequencer toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources