LeanrIQ

Export an existing Studio CreativeDocument version to production JPEG or PNG; returns exact dimensions, URL, bytes and checksum. Omit versionId to resolve the current persisted active version. Does not generate or replace editable creative state.

export_creative

Idempotent

Export an existing Studio CreativeDocument version to production JPEG or PNG; returns exact dimensions, URL, bytes and checksum. Omit versionId to resolve the current persisted active version. Does not generate or replace editable creative state.. Classification: writes to Studio. Execution: synchronous. Task support: forbidden. 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

Name	Required	Default
`format`	No	jpeg
`seatId`	No
`quality`	No
`flightId`	No
`maxBytes`	No
`seatName`	No
`accountId`	No
`versionId`	No
`creativeId`	Yes
`sourceLocale`	No
`targetMarket`	No
`contentLocale`	No
`marketContext`	No
`targetMarkets`	No
`contentLocales`	No
`defaultContentLocale`	No
`marketLanguageProfile`	No
`resolvedContentLocale`	No
`languageVariantGroupId`	No
`requestedOutputLocales`	No
`supportedContentLocales`	No

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

addedInput schema / properties / flightId

Added value: +{
+  "maxLength": 240,
+  "minLength": 1,
+  "type": "string"
+}

AddedOct 13, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=false), the description adds real operational context: synchronous execution, task support forbidden, partial-failure policy 'completed_items_not_rolled_back,' deterministic idempotency-key derivation on replay, and the rule that seatId/seatName must be supplied on the exact write call. These are meaningful traits the annotations do not convey, though the 'writes to Studio' classification and generic orchestration guidance are boilerplate.

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 duplicates the title verbatim (including a doubled period) and then appends a large block of generic orchestration boilerplate about assistantSummary and never displaying raw JSON that is not specific to exporting. Every sentence does not earn its place for this tool.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and the description does cover the versionId default and seat authorization. However, for a 21-parameter, nested-object tool with 0% schema description coverage, the description leaves most inputs unexplained, so it is only partially complete given the tool's complexity.

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 description coverage is 0% across 21 parameters, so the description carries the full burden and largely fails it. It clarifies versionId omission semantics and the seatId/seatName requirement, but leaves the export-defining parameters (format, quality, maxBytes, flightId, accountId, locale/market fields) entirely undocumented, and it references 'Mutation modes' for which no schema parameter exists.

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 opening sentence names a specific verb and resource (export an existing Studio CreativeDocument version) and the artifact produced (production JPEG or PNG), and it explicitly rules out adjacent behaviors with 'Does not generate or replace editable creative state,' which separates it from siblings like create_creative_version, generate_preview_links, and traffick_creative. It is clear, though it largely restates the title verbatim rather than adding new framing.

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?

The description implies usage via 'Omit versionId to resolve the current persisted active version' and the negative boundary 'Does not generate or replace editable creative state,' but it never names a concrete alternative tool or the condition that would select one (e.g., export_trafficked_assets vs. generate_preview_links). Guidance is inferable rather than explicit.

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?