Skip to main content
Glama

Retiplex

by com.retiplex
OverviewDiscussionsAdmin

Set product

set_product
Destructive

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

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 (5 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. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare this is a destructive, open-world mutation, but the description does not explain what existing product/media is replaced, whether changes are reversible, or any credit/auth implications. 'Changes' and 'adds' only restate the mutation at a high level.

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 definition is very short and front-loads the main actions. The second sentence is concise but of limited value because it relies on knowledge of another tool.

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 six-parameter destructive mutation with no output schema and only partial schema coverage, the description is too sparse. It omits usage conditions, destructive effects, and meaningful parameter explanation, leaving the agent dependent on the schema and sibling tools.

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?

Schema coverage is 67%, but the description adds no parameter meaning beyond the schema. 'Same inputs as create_project' is a vague cross-reference and does not compensate for undescribed fields such as product_name and product_type.

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 specific actions: changing a project's product and adding photos/videos. It is understandable apart from vague product terminology and does not clearly distinguish itself from sibling update_product_media.

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?

It gives no guidance on when to use this tool versus create_project or update_product_media. 'Same inputs as create_project' describes input shape, not usage conditions or exclusions.

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

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