Skip to main content
Glama

Change a promo

update_promo

Changes a promo by name: its lines (your words, a rewrite of one part with a note, or both in one change for different parts), the recipe, the feature's name, old screens (or not_old), screens wrongly taken for store images (not_marketing), taps made from two screenshots (pairs), store links, its notes (what it should say; lines the writer wrote are written again for them), new material (gather: box the cards on new screens and take a ready recording's frames, at the gather's prices), the screen in a scene, more app pages, the recipe, the bed, voice on or off, SFX on or off, the sizes. Timing, camera and motion are fixed. One round at a time: while the promo is working (gathering, or its draft or finals rendering) a change is refused; get_promo until it settles. Re-renders the 9:16 draft, paying only for the scenes that changed (3 credits per started 2 s) and 10 to put it together, plus any material the round buys (draft_916.material); estimate_only gives that price first. Returns the promo as get_promo does.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "promo_id": "<promo_id>"
    },
    "name": "update_promo"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesNoYour own words for some parts; the rest stay
notesNoWhat the promo should say; lines the writer wrote are written again for it
pairsNoUp to 3 taps or clicks, each from two of the person's screenshots of the same screen (a phone app's tap scene, or a click on a web app): 2 credits each when made, nothing if the control isn't found
sizesNoThe finals' sizes, for render_promo
slotsNoThe screen or cards in a scene, by slot (list_recipes names each recipe's slots)
soundNoMusic, sound effects and voice
gatherNoAlso box new screens' cards and take a ready recording's frames (priced)
lineupNoOne of the recipe's line-ups (list_recipes lists each with what it requires). Left out, the first the material meets; when none is met, the promo says what to send. A Quick line-up (list_recipes marks it) is used only when named, and sets its recipe; the promo stays Quick until a full line-up is named or null is passed, which goes back to the first full line-up the material meets
recipeNoThe recipe: saas (a web app), mobile (a phone app), feature-launch (a new feature of a product) or ecom (a product in an online shop). Left out, the tool picks from what it is given and says which
renderNoRe-render the 9:16 draft (default true; only the changed scenes are paid for)
storesNoA phone app's store pages: the end card shows each store's badge
featureNoThe new feature's name, as the product calls it (feature launch)
not_oldNoAsset ids of screens marked old by mistake: they become current screens again
productNoThe product as the person gives it: for marketplaces, or a shop capture can't read. Shown as given, marked as theirs. On a promo that has one, the fields left out are kept, even when the name changes: for another product, give each field (null for none)
rewriteNoHave the writer rewrite one part, with a note; every other part stays. It can go with lines for other parts in the same change
promo_idYesThe promo's id
app_pagesNoMore public pages to capture that show the product itself working (a public demo, tool or dashboard page), never the home page, product marketing or pricing (those go in site_pages, for a Quick promo)
site_pagesNoQuick promos only: up to 3 public pages of the person's own site to make it from, 2 credits a page. Left out, the address itself. Home, product and pricing pages belong here, never in app_pages
old_screensNoScreenshots of the product from before the feature, the same kind of screen as the new ones (feature launch); they are only ever shown as the before
product_pageNoThe product's own page in the shop (ecom), e.g. https://shop.example/products/tote; captured with its photos, price and rating at 2 credits. null takes it off the promo
wait_secondsNo
estimate_onlyNoPrice the change and spend nothing
not_marketingNoAsset ids of screens taken for a store's marketing images by mistake: they are used as app screens again
other_productsNoUp to 3 other product pages from the same shop, for the grid (ecom); 2 credits each
remove_app_pagesNoApp pages to drop from the promo by their address, e.g. a page that couldn't be captured or isn't the product itself; the scenes that picked them pick again

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / app_pages / description
      Previous value: -"More public pages to capture that show the product itself working (a public demo, tool or dashboard page), never the home page, product marketing or pricing"New value: +"More public pages to capture that show the product itself working (a public demo, tool or dashboard page), never the home page, product marketing or pricing (those go in site_pages, for a Quick promo)"
    • addedInput schema / properties / lineup / anyOf
      Added value: +[
      +  {
      +    "maxLength": 40,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / lineup / description
      Previous value: -"One of the recipe's line-ups (list_recipes lists each with what it requires). Left out, the first the material meets; when none is met, the promo says what to send"New value: +"One of the recipe's line-ups (list_recipes lists each with what it requires). Left out, the first the material meets; when none is met, the promo says what to send. A Quick line-up (list_recipes marks it) is used only when named, and sets its recipe; the promo stays Quick until a full line-up is named or null is passed, which goes back to the first full line-up the material meets"
    • removedInput schema / properties / lineup / maxLength
      Removed value: -40
    • removedInput schema / properties / lineup / minLength
      Removed value: -1
    • removedInput schema / properties / lineup / type
      Removed value: -"string"
    • addedInput schema / properties / site_pages
      Added value: +{
      +  "description": "Quick promos only: up to 3 public pages of the person's own site to make it from, 2 credits a page. Left out, the address itself. Home, product and pricing pages belong here, never in app_pages",
      +  "items": {
      +    "maxLength": 2048,
      +    "type": "string"
      +  },
      +  "maxItems": 3,
      +  "type": "array"
      +}
    • changedInput schema / properties / slots / items / properties / slot / enum
      Previous value: -[
      -  "hook",
      -  "brand",
      -  "flow",
      -  "dive",
      -  "growth",
      -  "lift",
      -  "stack",
      -  "cta",
      -  "change",
      -  "phone",
      -  "tap",
      -  "hero",
      -  "detail",
      -  "offer",
      -  "rating",
      -  "grid",
      -  "walk"
      -]New value: +[
      +  "hook",
      +  "brand",
      +  "flow",
      +  "dive",
      +  "growth",
      +  "lift",
      +  "stack",
      +  "cta",
      +  "change",
      +  "phone",
      +  "tap",
      +  "hero",
      +  "detail",
      +  "offer",
      +  "rating",
      +  "grid",
      +  "walk",
      +  "front"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Beyond the annotations it discloses the cost model (3 credits per started 2 s of changed scenes, 10 to assemble, 2 credits per pair or captured page, extra material billed via draft_916.material), the async lock that refuses changes while gathering/rendering, and the side effect that a re-render is triggered by default. It also confirms the non-destructive merge semantics ("the fields left out are kept"), consistent with destructiveHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded, but the first sentence is an 80-word run-on enumerating fifteen fields with inconsistent naming, which is hard to parse. The trailing sentences on timing, credits and return value are efficient and well ordered, so the waste is concentrated rather than pervasive.

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 25-parameter mutation tool with no output schema, the definition covers the important unknowns: cost, async refusal, re-render side effect, merge semantics of omitted fields, and the return value ("as get_promo does"). Auth or balance preconditions are not stated, but nothing an agent needs to invoke it correctly is missing.

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 96%, so nearly every one of the 25 parameters is already documented, and the baseline is 3. The description does add cross-parameter meaning the schema cannot, notably that lines and rewrite can be combined in one change for different parts, and that sizes feed render_promo. But most mappings are compressed to fragments ("the bed", "old screens (or not_old)", "the sizes") that add little beyond the schema text.

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?

The opening sentence names a specific verb and resource ("Changes a promo by name") and enumerates the mutable surface: lines, recipe, slots, stores, sound, sizes. It is distinguishable from get_promo and render_promo, both of which it names. The parenthetical naming is terse and occasionally cryptic ("the bed", "the recipe"), which keeps it short of a 5.

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?

It gives a real when-not rule: "One round at a time: while the promo is working ... a change is refused; get_promo until it settles," and routes to estimate_only for pricing. However, it never tells the agent when to reach for this broad update tool versus the finer-grained siblings (update_scene, update_short, update_graphic) — the choice is left to inference.

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