LeanrIQ

Create an advertiser-aware pre-roll or CTV video composition with varied executable scene layouts and channel constraints. It never claims an MP4 master or traffic-ready asset before Studio has rendered and certified one.

build_videoad

Idempotent

Create an advertiser-aware pre-roll or CTV video composition with varied executable scene layouts and channel constraints. It never claims an MP4 master or traffic-ready asset before Studio has rendered and certified one.. Classification: creates billable AI usage. Execution: durable. Task support: optional. Mutation modes: validate_only, preview_only, execute. Partial failure policy: completed_items_not_rolled_back. The returned JSON is internal application state for LeanrIQ and ChatGPT orchestration. Use assistantSummary first when responding to the user. Never display raw JSON, data, or meta unless the user explicitly asks for raw JSON. Mention IDs only when useful for follow-up or debugging. Prefer concise, human language, highlight the most useful insight, and suggest the next best LeanrIQ action. If idempotencyKey is omitted on a mutation, the MCP layer derives a deterministic retry key from the tool and business arguments so an accidental identical replay cannot create duplicate work. For a mutation when more than one seat is authorised, seatId or seatName must be supplied on that exact tool call; a remembered or previously selected seat is not sufficient for a write.

Input Schema

TableJSON Schema

Name	Required	Default
`cta`	No
`offer`	No
`seatId`	No
`channel`	Yes
`product`	No
`campaign`	No
`headline`	No
`seatName`	No
`accountId`	No
`objective`	Yes
`requestId`	No
`skippable`	No
`advertiser`	No
`campaignId`	No
`advertiserId`	No
`idempotencyKey`	No
`sourceAssetIds`	No
`supportingCopy`	No
`composeInStudio`	No
`contractVersion`	No	build-videoad-v1
`durationSeconds`	No
`studioCreativeId`	No
`sourceFrameImageUrls`	No
`expectedCreativeVersionId`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`meta`	Yes
`error`	No
`status`	Yes
`assistantSummary`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 6, 2026

addedInput schema / properties / advertiser

Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedInput schema / properties / campaign

Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedInput schema / properties / sourceFrameImageUrls

Added value: +{
+  "items": {
+    "maxLength": 4000,
+    "type": "string"
+  },
+  "maxItems": 3,
+  "type": "array"
+}

AddedOct 5, 2026

TDQS

A3.6/5.0

Behavior5/5

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

The description adds substantial behavior beyond the annotations: it flags billable AI usage, durable execution, optional task support, the three mutation modes, a partial-failure policy (completed_items_not_rolled_back), and the guarantee that no MP4 master is claimed before Studio renders and certifies one. It also explains the idempotency fallback and the exact-call seat requirement, which annotations alone do not cover. This is richer context than the readOnly/idempotent hints provide.

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

Conciseness3/5

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

The purpose is front-loaded, but the description balloons with orchestration boilerplate about how to phrase responses to the user and display rules that are tangential to invoking this specific tool, plus a duplicated sentence-ending period after "certified one..".

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

Completeness4/5

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

For a complex mutation with an output schema present, the description covers the failure policy, idempotency, seat authorization, and mode behavior, so an agent has enough to call it safely. The main shortfall is the near-total absence of parameter-level semantics across 24 fields.

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 24 parameters and 0% schema description coverage, the description should carry the semantics, but it only explains idempotencyKey and the seatId/seatName requirement. The remaining ~21 parameters (channel, objective, durationSeconds, sourceAssetIds, composeInStudio, etc.) are left entirely to the bare schema, leaving a large gap.

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 verb ("Create") and resource ("advertiser-aware pre-roll or CTV video composition") with channel constraints, which distinguishes it from generic build_ad and build_dooh siblings. It does not explicitly name those siblings, but the pre-roll/CTV framing is specific enough for an agent to select it correctly.

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

Usage Guidelines3/5

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

It conveys execution modes (validate_only, preview_only, execute) and the seat requirement for writes, which imply usage conditions. However, there is no explicit guidance on when to choose this over build_ad, build_dooh, or leanriq_build_ad, and no stated prerequisites or exclusions beyond seatId/seatName.

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

All LeanrIQ 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.

Resources

Need Help?