Skip to main content
Glama

Claude Imagine

by com.claudeimagine
OverviewDiscussionsAdmin

Plan a Product Ad

plan_product_ad
Read-onlyIdempotent

Plan a complete product-photo workflow: two image directions from one original product photo, user selection, then a short video. Returns exact account prices, prompts, budget guidance and output checks. Free: never starts a generation. Use before making product ads or product videos.

Input Schema

NameRequiredDescriptionDefault
productYesProduct name or short description
durationNoClip length in seconds. Must be supported by video_model; use list_models to see valid durations. Omitted uses the model default.
preserveNoProduct details that must stay unchanged
image_urlNoPublic URL of the original product photo. If absent, the plan explains how to upload on the website.
max_creditsNoTotal budget in credits for the whole workflow (two images and one clip, retries included). The plan says STOP when the itemized total is above it. This call itself costs nothing.
video_modelNoChoose any supported image-to-video model. If omitted, uses the free H3 preset when eligible, otherwise the cheapest preset supporting the requested duration.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / video_model / enum
      Previous value: -[
-  "h3-max-turbo",
-  "grok-imagine",
-  "seedance-1.5-pro",
-  "seedance-2.0-mini",
-  "veo-3.1-fast",
-  "kling-2.5-turbo"
-]New value: +[
+  "h3-max-turbo",
+  "grok-imagine",
+  "seedance-2.0-mini",
+  "veo-3.1-fast",
+  "kling-2.5-turbo"
+]
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false, and the description reinforces this with 'Free: never starts a generation.' It also discloses what it returns (exact account prices, prompts, budget guidance, output checks), adding value beyond annotations.

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-loaded with the workflow definition, then usage and cost disclaimers. Three sentences plus a short fragment; every sentence earns its place, though the 'Free: never starts a generation' fragment is slightly clipped.

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?

For a read-only planning tool with no output schema, the description covers what is returned (prices, prompts, budget guidance, output checks) and how image_url absence is handled. Nothing needed to call 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 100%, so the schema already documents all six parameters thoroughly. The description mentions budget guidance and image directions but adds no syntax or format details beyond what the schema provides.

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: 'Plan a complete product-photo workflow' with two image directions, user selection, and a short video. This clearly separates it from siblings like generate_image, generate_video, and quote_generation.

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

Usage Guidelines4/5

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

Explicitly says 'Use before making product ads or product videos,' giving a clear usage context. It doesn't name a specific sibling alternative for comparison, but the sequencing guidance is clear.

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

All Claude Imagine 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