Skip to main content
Glama

Siren

by ai.mysiren
OverviewDiscussionsAdmin

render_asset

Render films from pre-formed SirenSeed bodies (advanced). FILMS ONLY: images are painted from a brief, so for any image, ad or creative call create_campaign with asset_type=card (a still here returns 422 stills_use_a_brief). Each item: {output_type, channel, seed_body, archetype?, family?, surface?, caption?, voice_id?, music?, direction?, brand_override?}. Prefer create_campaign unless the user has concrete seed JSON. Returns run ids, estimated_seconds and poll_after_seconds; wait that long, then get_run.

THE DIRECTOR: every film body is edited against Brand DNA before it renders. It keeps the film and your brand-specific lines, rewrites empty, generic or reference-body copy, and never touches media. director in the response says what changed. direction is a free line ("dark, club energy, fast") that steers words, pace and music. A film that cannot use what you sent returns 422 film_does_not_fit with a fix and films_that_fit.

ANY BRAND: put brand_override={"name": "Acme", "site": "acme.com", "logo_url": "https://acme.com/logo.png", "primary": "#FF4400", "accent": "#111111"} on an item to render it for a brand that is not this workspace's own. With a name it is a clean slate: none of this workspace's logo, mascot, font, handle, screenshots or stills are used. Media slots take only URLs you uploaded with upload_media.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoHuman-readable name for the asset or run.
itemsYesPre-formed SirenSeed film bodies to render (films only; images go through create_campaign). Each item: {output_type, channel, seed_body, archetype?, family?, surface?, caption?, voice_id?, music?, direction?, brand_override?}. music = a bed track_id (omit and the bed follows the film and brand). direction = one free line that steers words, pace and music. brand_override with a name = render for ANOTHER brand, clean slate: {name, site, logo_url, primary, accent, secondary, tagline, font, x_handle}.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / items / description
      Previous value: -"Pre-formed SirenSeed bodies to render. Each item: {output_type, channel, seed_body, archetype?, family?, surface?, caption?, voice_id?, music?, direction?, brand_override?}. music = a bed track_id (omit and the bed follows the film and brand). direction = one free line that steers words, pace and music. brand_override with a name = render for ANOTHER brand, clean slate: {name, site, logo_url, primary, accent, secondary, tagline, font, x_handle}."New value: +"Pre-formed SirenSeed film bodies to render (films only; images go through create_campaign). Each item: {output_type, channel, seed_body, archetype?, family?, surface?, caption?, voice_id?, music?, direction?, brand_override?}. music = a bed track_id (omit and the bed follows the film and brand). direction = one free line that steers words, pace and music. brand_override with a name = render for ANOTHER brand, clean slate: {name, site, logo_url, primary, accent, secondary, tagline, font, x_handle}."
  2. Changed1 schema field changed
    • changedInput schema / properties / items / description
      Previous value: -"Pre-formed SirenSeed bodies to render. Each item: {output_type, channel, seed_body, archetype?, family?, surface?, caption?, voice_id?, music?, brand_override?}. music = a bed track_id (omit and the bed follows the brand archetype). brand_override with a name = render for ANOTHER brand, clean slate: {name, site, logo_url, primary, accent, secondary, tagline, font, x_handle}."New value: +"Pre-formed SirenSeed bodies to render. Each item: {output_type, channel, seed_body, archetype?, family?, surface?, caption?, voice_id?, music?, direction?, brand_override?}. music = a bed track_id (omit and the bed follows the film and brand). direction = one free line that steers words, pace and music. brand_override with a name = render for ANOTHER brand, clean slate: {name, site, logo_url, primary, accent, secondary, tagline, font, x_handle}."
  3. Changed1 schema field changed
    • changedInput schema / properties / items / description
      Previous value: -"Pre-formed SirenSeed bodies to render. Each item: {output_type, channel, seed_body, archetype?, family?, surface?, caption?, voice_id?, brand_override?}. brand_override with a name = render for ANOTHER brand, clean slate: {name, site, logo_url, primary, accent, secondary, tagline, font, x_handle}."New value: +"Pre-formed SirenSeed bodies to render. Each item: {output_type, channel, seed_body, archetype?, family?, surface?, caption?, voice_id?, music?, brand_override?}. music = a bed track_id (omit and the bed follows the brand archetype). brand_override with a name = render for ANOTHER brand, clean slate: {name, site, logo_url, primary, accent, secondary, tagline, font, x_handle}."
  4. Changed1 schema field changed
    • changedInput schema / properties / items / description
      Previous value: -"Pre-formed SirenSeed bodies to render. Each item: {output_type, channel, seed_body, archetype?, family?, surface?, caption?, voice_id?}."New value: +"Pre-formed SirenSeed bodies to render. Each item: {output_type, channel, seed_body, archetype?, family?, surface?, caption?, voice_id?, brand_override?}. brand_override with a name = render for ANOTHER brand, clean slate: {name, site, logo_url, primary, accent, secondary, tagline, font, x_handle}."
  5. Changed2 schema fields changed
    • addedInput schema / properties / items / description
      Added value: +"Pre-formed SirenSeed bodies to render. Each item: {output_type, channel, seed_body, archetype?, family?, surface?, caption?, voice_id?}."
    • addedInput schema / properties / name / description
      Added value: +"Human-readable name for the asset or run."
  6. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations provide no safety signals, so the description carries full behavioral weight. It discloses the Director's Brand DNA editing behavior, that media is never touched, that a `director` field reports changes, and that incompatible films return 422 with fix and films_that_fit. It also explains brand_override clean-slate semantics and upload requirements.

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?

The description is long but densely organized into purpose, routing, item format, return flow, Director behavior, and brand override. It is front-loaded with the core action and the critical films-only constraint, and every section adds necessary operational detail.

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?

Covers when to use the tool, what inputs are valid, what happens during rendering, how errors are surfaced, how to poll results, and edge cases like rendering for another brand. With an output schema present, it appropriately focuses on behavior and workflow rather than restating return fields.

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?

The schema only documents `name` and a generic `items` array with additionalProperties, leaving nested item fields undocumented. The description defines the item shape and explains `direction`, `music`, and `brand_override` with concrete examples and behavioral consequences, fully compensating for the schema gap.

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 opens with 'Render films from pre-formed SirenSeed bodies (advanced)', giving a specific verb, resource, and scope. It then explicitly differentiates from siblings by stating films only and routing images to create_campaign with asset_type=card.

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?

Provides explicit routing: 'for any image, ad or creative call create_campaign with asset_type=card' and 'Prefer create_campaign unless the user has concrete seed JSON.' It also advises waiting poll_after_seconds before get_run and requires media URLs to come from upload_media.

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

All Siren 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