Skip to main content
Glama

Move to another brand

move_creation_to_brand
Idempotent

Move a film or a library creation (an image, an ad, a carousel) to another brand in the same workspace — for work made under the wrong brand. Free; nothing is made again. kind is "studio_video" (a film: its project_id) or "creation" (a library item); id is that id, or the library's own id ("studio-video:" / "job:", then kind may be left out). target_brand_id from list_brands. Find the item with find_creation or list_creations on the brand it is in now. A film still being made cannot move until it finishes. Returns the moved item with toBrand.

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": {
      "id": "<id>",
      "target_brand_id": "<target_brand_id>"
    },
    "name": "move_creation_to_brand"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe film's project_id, the creation id, or the library id (studio-video:<uuid> / job:<uuid>)
kindNostudio_video for a film, creation for a library item
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.
target_brand_idYesThe brand to move it to, from list_brands

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
      +  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes beyond the annotations (readOnly=false, idempotent=true, destructive=false) by stating the move is free, nothing is regenerated, and in-progress films are blocked. What it does not cover is permission/auth requirements or what happens to references/links pointing at the moved item, so it is strong but not exhaustive.

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-loads the verb and resource, then packs the parameter guidance into a dense but scannable sequence of clauses. Slightly run-on with heavy backtick/quote usage, but virtually no wasted sentences.

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?

Despite no output schema, it describes the return value ('the moved `item` with `toBrand`'), the failure case (film still rendering), and the id-resolution rules. An agent has everything needed to invoke this correctly.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning: how `kind` interacts with `id`, and that when `id` is a prefixed library id ('studio-video:<uuid>' / 'job:<uuid>') `kind` may be omitted. That conditional is not derivable from the schema alone.

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 specific verb and resource ('Move a film or a library creation … to another brand in the same workspace') and enumerates what counts as a creation (image, ad, carousel). The scope is precise enough that an agent can distinguish it from siblings like find_creation, list_creations, or upload_brand_asset without inspecting schemas.

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 the triggering condition explicitly ('for work made under the wrong brand'), names the prerequisite lookup tools (find_creation or list_creations on the current brand, list_brands for target_brand_id), and states a hard exclusion: a film still being made cannot move until it finishes.

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