Skip to main content
Glama

Create project

create_project

Starts a new video ad for a product. Give product_url to import it, or product_name and product_description; add photos and videos by URL with media. Returns the project and the next step.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoDefaults to the product name.
mediaNoProduct photos and videos to add by URL (in addition to any found on product_url). For local files use create_media_upload. Media requirements: - Photos: JPEG, PNG or WebP; at least 480×480 px; at most 15 MB. Clear, well-lit shots of the real product, one product per photo, no collages or heavy text overlays. - Videos: MP4 or MOV (H.264 recommended); 1–60 seconds; at most 50 MB; vertical 9:16 recommended. Clips play muted. A video only appears in the ad through a custom-footage moment (add_moment, type custom-footage): uploading it alone does nothing. - Physical products: tag every photo with the view it shows (front, left, rear, a 3/4 view…, `detail` for a close-up, `size-reference` for a scale shot). A front photo is strongly recommended. - `detail` photos, and every photo of a digital product or service, need a description (≤240 characters) of what they show. - At most 8 files per call.
languageNoAsk the user which language the ad is spoken in unless it is obvious (a Spanish market means "es"). Default en. One of: en (English), cs (Czech), nl (Dutch), de (German), it (Italian), pl (Polish), sk (Slovak), es (Spanish). Set it BEFORE the creative brief and script (create_project or set_narrator_voice): they are written in it.
product_urlNoThe product page. Its name, description, campaign facts and up to 3 photos are imported (7 credits).
product_nameNo
product_typeNo
video_qualityNoAsk the user first. standard (default, affordable) or premium (Seedance 2.5, most realistic; English only for now, so not with a non-English language). It also decides how set_actor casts the actor: premium casts them on Seedream 5.0, the only faces Seedance films.
language_accentNoOptional regional accent, e.g. "Castilian Spanish" or "Mexican Spanish". Defaults to a native accent of the language; changing the language clears it.
product_descriptionNoWhat the product is and does, factually, in 2–3 sentences.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / product_url / description
      Previous value: -"The product page. Its name, description, campaign facts and up to 3 photos are imported (5 credits)."New value: +"The product page. Its name, description, campaign facts and up to 3 photos are imported (7 credits)."
  2. Changed1 schema field changed
    • changedInput schema / properties / video_quality / description
      Previous value: -"Ask the user first. standard (default, affordable) or premium (Seedance 2.5, most realistic). It also decides how set_actor casts the actor: premium casts them on Seedream 5.0, the only faces Seedance films."New value: +"Ask the user first. standard (default, affordable) or premium (Seedance 2.5, most realistic; English only for now, so not with a non-English language). It also decides how set_actor casts the actor: premium casts them on Seedream 5.0, the only faces Seedance films."
  3. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish this is a non-destructive open-world write, so safety is covered. The description adds that it 'Returns the project and the next step', useful workflow context, but says nothing about credit costs (only the schema's product_url note mentions 7 credits), whether a project can be re-created, or what state it starts in.

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?

Three short sentences, front-loaded with the action, then the input paths, then the outcome. No redundancy and nothing padded.

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 9-parameter, zero-required creation tool, the description covers the primary path, the media path, and the return value. The heavy lifting on media formats, language ordering, and quality trade-offs is done by the rich schema, so remaining gaps are minor.

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 description coverage is 78%, so the baseline is 3, and the description earns above that by stating the either/or relationship between product_url and product_name/product_description and by routing media URLs to the `media` parameter. It leaves language, video_quality, and product_type entirely to the schema, which does handle them well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Starts a new video ad for a product', which is more precise than the title 'Create project'. It implicitly distinguishes the entry point of the workflow from downstream siblings like set_product or generate_script, but never names a sibling nor clarifies the relationship to set_product or create_media_upload.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear guidance on which inputs to supply ('Give product_url to import it, or product_name and product_description') and points at `media` for assets, but offers no when-to-use vs alternatives framing (e.g. when to call this versus set_product on an existing project, or how it differs from list_projects). Usage is implied rather than delimited.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources