LeanrIQ

Run canonical LeanrIQ Competitor Intelligence V2 for one advertiser-scoped competitor. Defaults match Studio: 90-day DISPLAY evidence and no mixed social/video banner inference. Without forceRefresh, an existing canonical result is reused when available. (deprecated alias)

leanriq_get_competitor_creative_intelligence

Idempotent

Run canonical LeanrIQ Competitor Intelligence V2 for one advertiser-scoped competitor. Defaults match Studio: 90-day DISPLAY evidence and no mixed social/video banner inference. Without forceRefresh, an existing canonical result is reused when available.. Deprecated alias for run_competitor_intelligence. 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
`name`	No
`limit`	No
`domain`	No
`market`	No
`region`	No
`seatId`	No
`markets`	No
`website`	No
`seatName`	No
`brandName`	No
`advertiserId`	No
`competitorId`	No
`evidenceMode`	No	DISPLAY
`forceRefresh`	No
`lookbackDays`	No
`strategyMode`	No	BOTH
`evidenceLimit`	No
`strategyModes`	No
`targetMarkets`	No
`competitorName`	No
`competitorDomain`	No
`competitorWebsite`	No
`competitorKeyMessages`	No
`competitorPositioning`	No
`advertiserGuidanceSnapshot`	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.

Changed2 schema fields changedSep 1, 2026

addedInput schema / properties / competitorKeyMessages

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

addedInput schema / properties / competitorPositioning

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

Changed2 schema fields changedAug 14, 2026
- changedInput schema / properties / evidenceLimit / maximum
```
Previous value: -24New value: +48
```
- changedInput schema / properties / limit / maximum
```
Previous value: -24New value: +48
```

Changed24 schema fields changedAug 13, 2026

removedInput schema / properties / adFormat

Removed value: -{
-  "default": "DISPLAY_IMAGE",
-  "enum": [
-    "DISPLAY_IMAGE",
-    "IMAGE",
-    "DISPLAY"
-  ],
-  "type": "string"
-}

addedInput schema / properties / advertiserGuidanceSnapshot

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

addedInput schema / properties / advertiserId

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

changedInput schema / properties / brandName / maxLength
```
Previous value: -120New value: +180
```

addedInput schema / properties / competitorDomain

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

addedInput schema / properties / competitorId

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

addedInput schema / properties / competitorName

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

addedInput schema / properties / competitorWebsite

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

addedInput schema / properties / domain

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

addedInput schema / properties / evidenceLimit

Added value: +{
+  "maximum": 24,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / evidenceMode

Added value: +{
+  "default": "DISPLAY",
+  "enum": [
+    "DISPLAY",
+    "CROSS_CHANNEL",
+    "BOTH"
+  ],
+  "type": "string"
+}

addedInput schema / properties / forceRefresh

Added value: +{
+  "default": false,
+  "type": "boolean"
+}

removedInput schema / properties / limit / default
```
Removed value: -120
```
changedInput schema / properties / limit / maximum
```
Previous value: -120New value: +24
```

addedInput schema / properties / lookbackDays

Added value: +{
+  "default": 90,
+  "maximum": 730,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / market

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  ]
+}

addedInput schema / properties / markets

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  ]
+}

addedInput schema / properties / name

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

addedInput schema / properties / strategyMode

Added value: +{
+  "default": "BOTH",
+  "enum": [
+    "REPLICATE",
+    "DIFFERENTIATE",
+    "BOTH"
+  ],
+  "type": "string"
+}

addedInput schema / properties / strategyModes

Added value: +{
+  "items": {
+    "enum": [
+      "REPLICATE",
+      "DIFFERENTIATE"
+    ],
+    "type": "string"
+  },
+  "maxItems": 2,
+  "type": "array"
+}

addedInput schema / properties / targetMarkets

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  ]
+}

removedInput schema / properties / vertical

Removed value: -{
-  "maxLength": 160,
-  "minLength": 1,
-  "type": "string"
-}

changedInput schema / properties / website / maxLength
```
Previous value: -255New value: +300
```

removedInput schema / required

Removed value: -[
-  "brandName",
-  "website"
-]

First observedAug 12, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Though annotations already cover read-only/destructive/idempotent hints, the description adds substantial behavioral context: it creates billable AI usage, supports validate_only/preview_only/execute mutation modes, has a partial failure policy, returns internal application state, and derives deterministic retry keys. This goes well beyond what the annotations 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 core purpose is front-loaded and clear, but the description then includes a dense block of generic operational policy (classification, execution, task support, mutation modes, partial failure policy, output formatting) that could be more compact or structured. Each sentence has value, but the overall text is longer than needed.

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?

For a tool with 25 parameters, zero schema description coverage, and numerous near-duplicate fields, the description is not complete enough for correct invocation. It does not explain which identifier to use, whether fields are alternatives or required, or how markets/targetMarkets and strategyMode/strategyModes relate. The output schema and annotations help, but the input selection semantics remain under-specified.

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 25 parameters and 0% schema description coverage, the description carries a heavy burden but only clarifies forceRefresh, the 90-day default, and DISPLAY evidence mode. It does not explain the relationships between advertiserId/competitorId and name/domain alternatives, nor the market/markets and strategyMode/strategyModes duplication, so the agent cannot confidently map all parameters.

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 opens with a specific verb and resource: 'Run canonical LeanrIQ Competitor Intelligence V2 for one advertiser-scoped competitor.' It also clarifies the scoping and default behavior, and explicitly marks the tool as a deprecated alias for run_competitor_intelligence, which distinguishes it from siblings.

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?

The description explicitly tells the agent that this is a deprecated alias for run_competitor_intelligence, which is a clear routing instruction. It also states when cached results are reused ('Without forceRefresh, an existing canonical result is reused when available') and documents execution constraints like synchronous execution and forbidden task support.

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?