Skip to main content
Glama

Set product

set_product
Destructive

Changes a project's product, or adds photos and videos to it. Same inputs as create_project.

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": {
      "project_id": "<project_id>"
    },
    "name": "set_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
project_idYesThe project's id.
product_urlNoThe product page. Its name, description, campaign facts and up to 3 photos are imported (7 credits).
product_nameNo
product_typeNo
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. First observed

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare destructive=true and openWorld=true, so the safety profile is supplied. The description adds that the tool can change the product or add media, but it does not explain what existing product data or media may be replaced, nor does it note costs or side effects.

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?

The description is short and front-loaded, with no wasted prose. The second sentence is less useful because it relies on cross-tool knowledge, but the overall structure is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation with media-upload complexity, the description is too sparse. It omits how product changes affect existing fields, how media interacts with moments, credit implications, and the relationship to sibling tools, leaving the schema to carry most of the context.

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

Parameters2/5

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

With six parameters and 67% schema description coverage, the description adds almost no parameter meaning. 'Same inputs as create_project' forces the agent to inspect another tool, and product_name/product_type remain undocumented in both the schema and the description.

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 description states a specific mutation: changing a project's product or adding photos/videos to it. It is clear enough to distinguish the core action, but it does not differentiate from siblings such as create_project or update_product_media beyond mentioning shared inputs.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use set_product versus create_project, update_product_media, or create_media_upload. 'Same inputs as create_project' describes schema similarity, not when to choose this tool over alternatives.

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