Skip to main content
Glama
Sign In

AutoShort

by org.autoshort
OverviewDiscussionsAdmin

autoshort_ugc_create_campaign

Idempotent

Create a Silent UGC campaign for the user's own app. Silent UGC: 9-12 s silent promo shorts for the user's OWN app. Scene 1 = one consistent FICTIONAL AI character (realistic, or faceless: hands on a phone / over-the-shoulder / back view) silently reacting with body language and a big hook in the upper third; scene 2 = the app's real screen recording with a short caption. No voice, no audio track (a trending sound is added when posting). Every video carries a visible "AI-generated" note and AI metadata; switch the platform AI label on when posting. Characters come only from a text description (no photo uploads), must be fictional adults (no real or public people, lookalikes or @handles) and non-sexual — the server refuses anything else. Flow: (0) autoshort_ugc_upload_recording (the app screen recording as a public https URL or base64 → recordingAssetId); (1) autoshort_ugc_create_campaign (app name, what it does, a character, recordingAssetId); (2) autoshort_ugc_suggest_hooks; (3) autoshort_ugc_preview ONE hook and show the still to the user; (4) after they approve, autoshort_ugc_render_batch with the hooks they picked; (5) poll autoshort_ugc_get_campaign for the finished videos. Pass characterId to reuse a character, or characterDescription (a fictional adult's look; never a real or public person, a lookalike or a @handle; nothing sexual) plus characterStyle ("face" = realistic fictional character, "faceless" = hands/over-the-shoulder only) to generate one (1 credit, charged before the image is made). recordingAssetId comes from autoshort_ugc_upload_recording (MP4/MOV, 3-60 s, max 50 MB). Free otherwise.

Input Schema

NameRequiredDescriptionDefault
goalNo
appUrlNoPublic URL of the app or its store page.
appNameYes
captionNoScene-2 caption, e.g. "type one idea… get a finished short".
characterIdNo
characterNameNo
appDescriptionYesWhat the app really does. Hooks are written only from this.
characterStyleNoRealistic fictional AI character (default when available) or faceless.
idempotencyKeyNoRetry-safe: a repeat with the same key returns the first answer (replayed: true) and creates nothing.
recordingAssetIdNo
characterDescriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (which cover readOnly/destructive/idempotent/openWorld), the description discloses that generating a character costs 1 credit charged *before* the image is made, that the rest is free, that content is server-side rejected if not a fictional, non-sexual adult, and that videos carry an AI-generated label/metadata. These are cost and refusal behaviors an agent cannot infer from structured fields.

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?

Front-loaded with purpose, then format spec, then flow, then parameter rules — a sensible order. It is long and repeats the silence/character-consistency constraints, but almost every sentence carries operational content rather than filler.

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 creation tool with no output schema, the description covers what is produced, media constraints (MP4/MOV, 3-60 s, 50 MB), cost, content policy, and the downstream steps needed to get finished videos. An agent has enough to start correctly and knows where to poll.

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 coverage is only 45%, so the description must carry weight, and it does add meaning for characterId, characterDescription, characterStyle, recordingAssetId, appName and appDescription. However goal (installs/trial/awareness), appUrl and characterName receive no explanation anywhere, leaving a real gap for 3 of 11 parameters.

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?

Opens with a specific verb and resource ("Create a Silent UGC campaign") and immediately defines the artifact: 9-12 s silent promo shorts with a two-scene structure. This is clearly distinguished from sibling ad/video generators like autoshort_generate_product_ad or autoshort_generate_video.

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?

Gives an explicit numbered flow from upload_recording through get_campaign polling, naming the exact sibling tools at each step and the precondition that recordingAssetId comes from autoshort_ugc_upload_recording. It also states the branch (pass characterId to reuse vs. characterDescription to generate), which is exactly the decision an agent must make.

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

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