LeanrIQ

LeanrIQ Creative Runtime: Default preview mode works without Studio and stores research, briefs, builds, QA, and previews in a LeanrIQ workspace. collaborate keeps proposals non-destructive; operate deliberately creates Studio work. Publish is never inferred: traffic_ready and publish remain explicit governed Studio actions. (deprecated alias)

leanriq_launch_creative_campaign

Idempotent

LeanrIQ Creative Runtime: Default preview mode works without Studio and stores research, briefs, builds, QA, and previews in a LeanrIQ workspace. collaborate keeps proposals non-destructive; operate deliberately creates Studio work. Publish is never inferred: traffic_ready and publish remain explicit governed Studio actions.. Deprecated alias for launch_creative_campaign. Classification: writes to Studio, creates billable AI usage, publishes externally. 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

TableJSON Schema

Name	Required	Default
`KPI`	No
`cta`	No
`tone`	No
`brand`	No
`force`	No
`offer`	No
`budget`	No
`seatId`	No
`channel`	No
`endDate`	No
`product`	No
`audience`	No
`elements`	No
`flightId`	No
`headline`	No
`platform`	No
`seatName`	No
`vertical`	No
`accountId`	No
`mustAvoid`	No
`objective`	Yes
`skippable`	No
`startDate`	No
`approvalId`	No
`campaignId`	No
`flightName`	No
`constraints`	No
`creativeIds`	No
`destination`	No
`funnelStage`	No
`mustInclude`	No
`persistence`	No
`targetSizes`	No
`workspaceId`	No
`advertiserId`	No
`campaignName`	No
`deliverables`	No
`saveToStudio`	No
`executionMode`	No	preview
`idempotencyKey`	No
`landingPageUrl`	No
`sourceAssetIds`	No
`supportingCopy`	No
`thirdPartyTags`	No
`durationSeconds`	No
`revisionRequest`	No
`workspaceSource`	No
`performanceEvidence`	No
`sourceFrameImageUrls`	No
`workspaceAccessToken`	No
`createCampaignIfMissing`	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.

Changed1 schema field changedOct 6, 2026

addedInput schema / properties / sourceFrameImageUrls

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

Changed6 schema fields changedOct 5, 2026

addedInput schema / properties / cta

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

addedInput schema / properties / durationSeconds

Added value: +{
+  "maximum": 120,
+  "minimum": 5,
+  "type": "integer"
+}

addedInput schema / properties / headline

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

addedInput schema / properties / skippable
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / sourceAssetIds

Added value: +{
+  "items": {
+    "maxLength": 240,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 50,
+  "type": "array"
+}

addedInput schema / properties / supportingCopy

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

Changed1 schema field changedOct 2, 2026

addedInput schema / properties / creativeIds

Added value: +{
+  "items": {
+    "maxLength": 240,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 24,
+  "minItems": 1,
+  "type": "array"
+}

Changed1 schema field changedSep 30, 2026

addedInput schema / properties / thirdPartyTags

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "creativeId": {
+        "maxLength": 240,
+        "minLength": 1,
+        "type": "string"
+      },
+      "name": {
+        "maxLength": 240,
+        "minLength": 1,
+        "type": "string"
+      },
+      "tag": {
+        "maxLength": 12000,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "tag"
+    ],
+    "type": "object"
+  },
+  "maxItems": 3,
+  "type": "array"
+}

First observedAug 12, 2026

TDQS

A3.6/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnly=false, idempotent=true, destructive=false, openWorld=true) by disclosing billable AI usage, external publishing, synchronous execution, forbidden task support, partial-failure policy of completed_items_not_rolled_back, deterministic idempotency-key derivation on replay, and the requirement to pass seatId/seatName on write calls. These are exactly the operational traits an agent needs before a governed write.

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 definition is long and partly redundant – the title paragraph is essentially repeated verbatim at the start of the description (including a doubled period '..'), and return-formatting instructions sit alongside mode semantics. Useful content is present but not front-loaded around the tool's core action.

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 51-param, high-risk governed write with an output schema, the description supplies the behavioral context that structured fields cannot (billing, publishing, partial-failure, idempotency, seat requirements) and correctly leaves return values to the output schema. The main gap is the near-total absence of per-parameter meaning.

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 51 parameters, so the description carries the full burden, yet it only adds meaning for executionMode, idempotencyKey, seatId/seatName, and persistence-adjacent modes. The other ~45 fields (brand, budget, KPI, deliverables, thirdPartyTags, workspaceSource, etc.) receive no semantic clarification, leaving most inputs undocumented.

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 name, title, and 'Deprecated alias for launch_creative_campaign' line make the resource (creative campaign launch) and its relationship to the canonical sibling explicit, so an agent can route to launch_creative_campaign instead. The opening runtime-mode paragraph is dense but describes launch semantics rather than restating the name. Clear verb+resource with sibling differentiation, though the leading prose obscures the purpose slightly.

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 explains execution modes (preview default, collaborate non-destructive, operate creates Studio work, publish explicit), which is genuine invocation guidance. However, for a deprecated alias it never tells the agent to prefer the canonical launch_creative_campaign, and gives no explicit when-not-to-use-this-tool statement. Guidance is implied rather than directive.

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?