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.

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.. 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
`tone`	No
`brand`	No
`force`	No
`offer`	No
`budget`	No
`seatId`	No
`channel`	No
`endDate`	No
`product`	No
`audience`	No
`elements`	No
`flightId`	No
`platform`	No
`seatName`	No
`vertical`	No
`accountId`	No
`mustAvoid`	No
`objective`	Yes
`startDate`	No
`approvalId`	No
`campaignId`	No
`flightName`	No
`constraints`	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
`revisionRequest`	No
`workspaceSource`	No
`performanceEvidence`	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. Dates show when Glama detected each change.

First observedAug 12, 2026

TDQS

C2.5/5.0

Behavior5/5

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

The description goes far beyond annotations by disclosing side effects: 'writes to Studio, creates billable AI usage, publishes externally', synchronous execution, partial failure policy, and detailed idempotency key behavior. It also clarifies seat requirements for mutations, providing rich behavioral context.

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

Conciseness1/5

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

The description is a long, unstructured block of text that mixes runtime policies with response-style guidelines ('Use assistantSummary first...'). It is not front-loaded with a clear tool summary and includes extraneous instructions better suited to a system prompt.

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

Completeness2/5

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

Given the tool's complexity (42 parameters, output schema), the description omits the core purpose and parameter orchestration. It covers operational quirks like idempotency and partial failure, but leaves major gaps about what the tool does and how to invoke it correctly.

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?

Only `idempotencyKey` and `seatId`/`seatName` receive some explanatory context, while the schema has 42 parameters with zero embedded descriptions. The description fails to compensate for the low schema coverage for critical parameters like `objective`, `executionMode`, `persistence`, or `workspaceSource`.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a generic runtime overview ('LeanrIQ Creative Runtime...') and never explicitly states that `launch_creative_campaign` launches a creative campaign. It lists modes and policies but does not specify the tool's core action or scope, making it unclear what the tool does.

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

Usage Guidelines2/5

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

There is no explicit 'use this tool when...' or comparison to sibling tools. The description mentions mutation modes and 'Task support: forbidden' but does not explain when to choose this tool over alternatives like `build_ad` or `create_campaign`.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.6/5.0

Disambiguation2/5

The tool set is dominated by deprecated aliases (leanriq_build_ad, leanriq_create_brief, etc.) that duplicate canonical tools exactly, and multiple high-level builders (build_ad, build_campaign_creative_set, leanriq_campaign_builder, launch_creative_campaign) overlap in purpose. An agent would struggle to pick the intended tool without inspecting full descriptions.

Naming Consistency2/5

Canonical tools follow a sensible verb_noun pattern (create_campaign, get_creative, list_flights), but the large number of 'leanriq_' prefixed aliases and special names like leanriq_campaign_builder create a mixed, inconsistent surface. The presence of both build_ad and leanriq_build_ad, or get_current_seat and leanriq_current_seat, breaks any predictable convention.

Tool Count1/5

87 tools is an extreme number for any MCP server, even a broad ad-platform API. The sheer volume, including many duplicate aliases, far exceeds a well-scoped set and will overwhelm agents with unnecessary choices.

Completeness4/5

The core lifecycle is well covered: CRUD for advertisers, campaigns, flights, creatives, versions, assets, plus trafficking, QA, preview, and publishing. Minor gaps exist, such as the missing canonical create_creative_strategy (only a deprecated alias references it) and no direct update_creative, but the domain is functionally complete.

Resources

Need Help?