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: durable. Task support: optional. 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

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
`sourceLocale`	No
`strategyMode`	No	BOTH
`targetMarket`	No
`contentLocale`	No
`evidenceLimit`	No
`marketContext`	No
`strategyModes`	No
`targetMarkets`	No
`competitorName`	No
`contentLocales`	No
`competitorDomain`	No
`competitorWebsite`	No
`recommendationMode`	No	FULL
`defaultContentLocale`	No
`competitorKeyMessages`	No
`competitorPositioning`	No
`marketLanguageProfile`	No
`resolvedContentLocale`	No
`languageVariantGroupId`	No
`requestedOutputLocales`	No
`supportedContentLocales`	No
`advertiserGuidanceSnapshot`	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.

Changed15 schema fields changedOct 13, 2026

addedInput schema / properties / contentLocale
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / contentLocales

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

addedInput schema / properties / defaultContentLocale
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / languageVariantGroupId

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

addedInput schema / properties / marketContext

Added value: +{
+  "properties": {
+    "currency": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "targetMarket": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "targetMarkets": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "timeZone": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / marketLanguageProfile

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

addedInput schema / properties / requestedOutputLocales

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

addedInput schema / properties / resolvedContentLocale
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / sourceLocale
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / supportedContentLocales

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

addedInput schema / properties / targetMarket

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

removedInput schema / properties / targetMarkets / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  }
-]

addedInput schema / properties / targetMarkets / items

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

addedInput schema / properties / targetMarkets / maxItems
```
Added value: +50
```
addedInput schema / properties / targetMarkets / type
```
Added value: +"array"
```

Changed1 schema field changedOct 7, 2026

addedInput schema / properties / recommendationMode

Added value: +{
+  "default": "FULL",
+  "enum": [
+    "FULL",
+    "EVIDENCE_ONLY"
+  ],
+  "type": "string"
+}

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

B3.2/5.0

Behavior4/5

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

Beyond annotations, it adds high-value context: 'creates billable AI usage,' 'Execution: durable,' 'Task support: optional,' and a partial failure policy (completed_items_not_rolled_back). It also explains idempotencyKey derivation for accidental replays. These are meaningful behavioral facts the annotations do not carry.

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

Conciseness2/5

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

The useful purpose sentence is front-loaded, but it is followed by a long tail of metadata (classification, execution, mutation modes, partial failure policy) and generic response-formatting boilerplate ('Never display raw JSON,' 'Use assistantSummary first') that is not specific to this tool. A doubled period also signals sloppy templating.

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 needn't be described, and the description covers caching/defaults, billable classification, and partial-failure semantics. However, for a 37-parameter, zero-coverage tool with nested objects it still leaves most input semantics undocumented, so it is only adequate rather than complete.

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 37 parameters at 0% schema description coverage, the description only touches a few: forceRefresh behavior, the DISPLAY/90-day defaults (evidenceMode, lookbackDays), and idempotencyKey. The vast majority of business-critical inputs (advertiserId, competitorId, seatId, strategyMode, etc.) are unexplained in both schema and description.

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 description states a specific verb and resource: 'Run canonical LeanrIQ Competitor Intelligence V2 for one advertiser-scoped competitor,' and identifies the sibling it aliases ('Deprecated alias for run_competitor_intelligence'). This lets an agent distinguish it, though the name prefix 'get_' conflicts with the actual run/mutation nature.

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 discloses a key selection condition ('Without forceRefresh, an existing canonical result is reused when available') and mentions mutation modes (validate_only, preview_only, execute). But it never explicitly directs the agent to prefer the canonical run_competitor_intelligence tool over this deprecated alias, leaving that inference to the reader.

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?