LeanrIQ

Plan and create an initial Studio creative set for a campaign that has no saved creatives. Do not use this tool to rebuild existing creatives; use build_ad with campaignId or campaignName, which resolves and rebuilds the full saved Studio inventory. (deprecated alias)

leanr_build_campaign_creative_set

Idempotent

Plan and create an initial Studio creative set for a campaign that has no saved creatives. Do not use this tool to rebuild existing creatives; use build_ad with campaignId or campaignName, which resolves and rebuilds the full saved Studio inventory.. Deprecated alias for build_campaign_creative_set. Classification: creates billable AI usage. 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.

Input Schema

TableJSON Schema

Name	Required	Default
`KPI`	Yes
`brand`	No
`notes`	No
`budget`	No
`seatId`	No
`billing`	No
`channel`	No	display
`endDate`	No
`sandbox`	No
`audience`	Yes
`operator`	No
`seatName`	No
`accountId`	No
`objective`	Yes
`startDate`	No
`campaignId`	No
`doohContext`	No
`funnelStage`	Yes
`targetSizes`	No
`advertiserId`	No
`campaignName`	Yes
`generateTags`	No
`saveToStudio`	No
`idempotencyKey`	No
`desiredVariantCount`	No
`strictBrandCompliance`	No
`createAdvertiserIfMissing`	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.

Changed2 schema fields changedSep 28, 2026

addedInput schema / properties / channel

Added value: +{
+  "default": "display",
+  "enum": [
+    "display",
+    "dooh"
+  ],
+  "type": "string"
+}

addedInput schema / properties / doohContext

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

First observedAug 12, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Despite annotations covering safety (readOnly=false, idempotent=true, destructive=false), the description adds substantial context: billable AI usage, synchronous execution, forbidden task support, the three mutation modes (validate_only, preview_only, execute), the partial-failure policy (completed_items_not_rolled_back), and how idempotencyKey is derived on omission.

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

Conciseness4/5

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

Front-loaded with purpose and exclusions, then behavioral contract, then response-formatting guidance. It is densely packed but the title redundantly restates the opening sentence, and the raw-JSON/assistantSummary guidance is verbose relative to the calling decision.

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 high-complexity, 27-parameter mutation tool with an output schema, the description covers the behavioral contract (billing, mutation modes, failure policy, idempotency) and output handling guidance well. Its main gap is the near-total absence of parameter semantics, which the schema also fails to supply.

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 27 parameters, and the description explains only idempotencyKey's derivation behavior. Required inputs like KPI, audience, funnelStage, objective and the semantics of flags such as saveToStudio, strictBrandCompliance, and createAdvertiserIfMissing go undocumented in both places.

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?

The description states a specific verb and resource ('Plan and create an initial Studio creative set') and narrows the scope to 'a campaign that has no saved creatives'. It explicitly distinguishes itself from build_ad, which rebuilds the saved Studio inventory, so an agent can route correctly without opening sibling schemas.

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

Usage Guidelines5/5

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

Both the when ('campaign that has no saved creatives') and the when-not ('Do not use this tool to rebuild existing creatives; use build_ad with campaignId or campaignName') are stated explicitly, with the alternative tool and its arguments named.

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?