designforyou

by org.swapp1990.designforyou

Create Actor

create_actor

Create a private LetMeActForYou actor draft. Generates a casting headshot, stores it on S3, and returns actor_id for cast_character or audition. Draft actors never appear in the public feed; an authorized operator can call publish_actor with an approved seamless idle-loop URL when the actor is ready. When available, provide a saved full-body standing performance_reference_url; all generated clips prioritize it over the profile headshot. The default casting template produces an original Pixar-quality 3D animated feature-film headshot; pass stable fictional physical identity, not performance direction. Apparent age may be child, teen, adult, or elderly.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`bio`	No
`name`	Yes
`emoji`	No
`actor_type`	No
`visual_description`	Yes	Stable physical identity for the actor headshot and later takes: apparent age (child, teen, adult, or elderly), ethnicity, facial structure, hair, build, and baseline wardrobe. Keep identities fictional. Use one concise identity description only; do not include a scene, cue, dialogue, camera direction, other people, props, logos, or a request to imitate an existing character.
`headshot_template_id`	No	Character References template used to generate the actor headshot.	acting_casting_headshot
`performance_reference_url`	No	Saved full-body standing reference image URL used as the starting frame for every performance clip. Keep this separate from the profile headshot.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 4, 2026

addedInput schema / properties / performance_reference_url

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 4000,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Saved full-body standing reference image URL used as the starting frame for every performance clip. Keep this separate from the profile headshot.",
+  "title": "Performance Reference Url"
+}

Changed1 schema field changedJul 13, 2026

changedInput schema / properties / visual_description / description

Previous value: -"Stable physical identity for the actor headshot and later takes: apparent age, ethnicity, facial structure, hair, build, and baseline wardrobe. Use one concise identity description only; do not include a scene, cue, dialogue, camera direction, other people, props, logos, or a request to imitate an existing character."New value: +"Stable physical identity for the actor headshot and later takes: apparent age (child, teen, adult, or elderly), ethnicity, facial structure, hair, build, and baseline wardrobe. Keep identities fictional. Use one concise identity description only; do not include a scene, cue, dialogue, camera direction, other people, props, logos, or a request to imitate an existing character."

AddedJul 12, 2026
RemovedJul 11, 2026

Changed2 schema fields changedJul 11, 2026

addedInput schema / properties / headshot_template_id

Added value: +{
+  "default": "acting_casting_headshot",
+  "description": "Character References template used to generate the actor headshot.",
+  "maxLength": 100,
+  "minLength": 1,
+  "title": "Headshot Template Id",
+  "type": "string"
+}

changedInput schema / properties / visual_description / description

Previous value: -"Stable physical identity for the actor headshot and later takes: apparent age, face, hair, build, and baseline wardrobe."New value: +"Stable physical identity for the actor headshot and later takes: apparent age, ethnicity, facial structure, hair, build, and baseline wardrobe. Use one concise identity description only; do not include a scene, cue, dialogue, camera direction, other people, props, logos, or a request to imitate an existing character."

AddedJul 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the disclosure adds significant behavioral context: generation of headshot, S3 storage, draft privacy, clip prioritization of performance_reference_url, and default template quality. This exceeds what annotations provide, though it doesn't cover all possible side effects like rate limits.

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 four sentences, each delivering distinct information: core purpose, draft/public workflow, performance reference guidance, and template/visual description guidance. It is front-loaded with the main purpose and contains zero wasted words.

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?

The description covers the creation flow, return value, draft state, publishing path, and key parameter guidance. It doesn't explain every minor parameter (bio, emoji, actor_type) but these are likely self-explanatory. Overall, it provides sufficient context for an agent to understand the tool's role and usage.

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?

The description adds valuable meaning to visual_description (stable physical identity, not performance direction) and performance_reference_url (full-body standing, prioritized). However, with schema coverage at only 43%, parameters like bio, emoji, and actor_type are left undocumented in both the schema and description, so the description doesn't fully compensate for the 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 clearly states the tool creates a private LetMeActForYou actor draft, generates a casting headshot, stores it on S3, and returns actor_id for cast_character or audition. This specific verb+resource+outcome clearly distinguishes it from siblings like publish_actor and cast_character.

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?

The description explains the draft workflow, noting that drafts never appear in the public feed and that publish_actor is used when the actor is ready. It also gives guidance on providing performance_reference_url when available. However, it doesn't explicitly name alternative creation tools or directly state 'use this instead of X', but the context is clear.

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

All designforyou tools Inspect

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.

Create Actor

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources