ai-content-drop

Estimate ad cost

estimate_ad_cost

Read-onlyIdempotent

Price a studio job before making it: a finished ad from a brief or storyboard (kind "ad"), a UGC creator video (kind "ugc"), a generated avatar (kind "avatar") or a competitor-ad decode (kind "decode"). Returns the credit lines, the total and a quote_id that generate_ad, generate_ugc_video, generate_avatar and decode_ad require. No account needed. For an ad, quote exactly the fields you will submit.

Input Schema

Name	Required	Description
`kind`	No	Defaults to ad.
`brief`	No	The ad brief: brandName, brandOneLiner, valueProps (1-8 strings), cta, intent, format (an id from list_ad_formats), shotCount (1-5), totalDurationSec (5-20), aspect (9:16 \| 16:9 \| 1:1), language, quality (fast \| premium), modelTier (standard \| cinematic), garmentImageUrl for the try-on formats.
`quality`	No	Lip-sync tier. premium costs more per talking shot. Defaults to the brief's quality, else fast.
`model_tier`	No	cinematic renders on Seedance with director-grade camera work and costs more per shot; needs the brief.
`storyboard`	No	The storyboard returned by write_ad_storyboard, as is or edited. When present it is what renders; the brief is optional alongside it.
`persona_mode`	No	synthetic lets the studio substitute one consistent generated creator for the avatar; exact-avatar (default) keeps the avatar as given.
`needs_avatar_gen`	No	True when the avatar still has to be generated (billed as a line).
`needs_product_gen`	No	True when the product still has to be generated (billed as a line).

Output Schema

Name	Required	Description
`kind`	Yes
`basis`	Yes
`lines`	Yes
`quote_id`	Yes	Signed quote. Pass it to the matching generate_* tool; it fixes the price and makes a retry safe.
`next_step`	Yes
`expires_at`	Yes	ISO time after which the quote is refused.
`credits_total`	Yes	For an ad, the most it can cost; the charge on success is never higher.
`expires_in_seconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 30, 2026

changedInput schema / properties / brief / description

Previous value: -"The ad brief: brandName, brandOneLiner, valueProps (1-8 strings), cta, intent, format (an id from list_ad_formats), shotCount (2-5), totalDurationSec (6-20), aspect (9:16 | 16:9 | 1:1), language, quality (fast | premium), modelTier (standard | cinematic), garmentImageUrl for the try-on formats."New value: +"The ad brief: brandName, brandOneLiner, valueProps (1-8 strings), cta, intent, format (an id from list_ad_formats), shotCount (1-5), totalDurationSec (5-20), aspect (9:16 | 16:9 | 1:1), language, quality (fast | premium), modelTier (standard | cinematic), garmentImageUrl for the try-on formats."

AddedSep 11, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Adds useful context beyond the read-only/idempotent annotations: it discloses the return contents (credit lines, total, quote_id), states no account is needed, and notes that the quote_id is required by generate_ad, generate_ugc_video, generate_avatar and decode_ad. It does not mention quote expiry or precision caveats, but the behavioral picture is solid.

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

Conciseness5/5

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

Three tight sentences, front-loaded with the purpose and kinds, followed by return values and the downstream dependency. Every sentence carries information an agent needs.

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?

Complete for a read-only estimator: it covers purpose, supported kinds, return shape, quote_id consumers and account requirements, while the output schema and 100% schema coverage carry the field-level detail. Nothing essential for correct invocation is missing.

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 meaning by mapping each kind value to a real use case and by advising "For an ad, quote exactly the fields you will submit," which helps align brief/storyboard inputs. It does not elaborate on the individual brief fields beyond the schema, so it stays just above baseline.

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 ("Price") and resource ("studio job") and immediately enumerates the four supported kinds with concrete examples, so an agent can distinguish it from generate_ad and the other generation siblings. The description makes clear this is an estimator, not a generator.

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 positions the tool as a preflight step ("before making it") and names the four downstream siblings that consume the returned quote_id, which is strong routing guidance. It does not explicitly state when not to use it, but the context is clear enough to avoid misuse.

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

All ai-content-drop tools Inspect

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.