Skip to main content
Glama
seocombat

Clipwright

by seocombat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create a personal actor

create_actor

Create a personal AI actor for UGC-style video ads from a text description. Starts generation immediately and returns a run ID to monitor success.

Instructions

Create a personal actor for this account from words describing a fictional adult: a 9:16 portrait with exactly one face, plus the other requested formats edited from it. Returns a run_id immediately; poll get_run until 'succeeded' (created_actor.actor_id, then pass it as actor_id to make_ugc) or 'failed'. Each published image is charged at the price quote shows; refused descriptions and unusable portraits cost nothing. When generation is switched off the call fails with actor_generation_disabled.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName shown in list_actors.
genderYesfemale | male. Fixes the actor's gender and the default voice of videos with this actor.
attemptNo
qualityNoImage quality: medium | high. Omitted means medium. The price per image depends on it; quote shows it before any charge.medium
descriptionYesWords describing a fictional adult: appearance, clothing, setting. Naming a real person or a likeness to one is refused before any charge (actor_prompt_refused).
aspect_ratiosNoFormats to create: 9:16 | 1:1 | 16:9, always including 9:16. Omitted means all three. Formats that fail the identity check are not charged and are named in warnings.
approximate_ageYesApproximate age in years, 18 to 90: actors are adults.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.20.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only indicate non-read-only and non-destructive; description adds the async behavior (returns run_id immediately, poll get_run), cost/refund semantics, and failure modes (actor_generation_disabled, actor_prompt_refused). These are substantive behavioral disclosures beyond 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?

Four dense sentences, front-loaded with purpose and output, then async flow, pricing, and failure modes. No filler; each sentence carries operational information needed for correct use.

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?

Covers the major operational facts an agent needs: async polling, success data flow, pricing, refusal/no-charge behavior, and disabled-generation failure. Lacks any explanation of the attempt parameter (also undocumented in schema), which is the main completeness gap given no output schema.

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

Parameters4/5

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

Schema already covers 6 of 7 parameters with descriptions, so the baseline is 3. The description adds semantic color by tying description to 'fictional adult', aspect_ratios to '9:16 portrait...edited from it', and quality to per-image pricing. It doesn't clarify the undocumented attempt parameter, so not a 5.

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 action (create a personal actor) and specifies inputs (words describing a fictional adult) and outputs (9:16 portrait plus formats, run_id). Clearly distinguished from siblings: it is the creation counterpart to list_actors/delete_actor, and its async flow is explicitly routed to get_run and make_ugc.

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 clear usage context, including the asynchronous polling workflow and how results connect to make_ugc. Does not explicitly state when not to use it or name alternatives such as quote_actor for price estimation before creation, so it stops short of a full 5.

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

Deploy Server

Other Tools