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
`recommendationMode`	No	FULL
`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.

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

A3.5/5.0

Behavior5/5

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

Goes well beyond the annotations, adding that the call creates billable AI usage, is synchronous, forbids task support, supports validate_only/preview_only/execute mutation modes, applies a completed_items_not_rolled_back partial failure policy, and derives a deterministic idempotency key on omitted mutation keys. These are exactly the behavioral traits an agent needs and are not present in the structured annotations.

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 substantive purpose and behavior facts are front-loaded, but a large fraction of the text is generic output-rendering boilerplate (assistantSummary, never display raw JSON, mention IDs only when useful) that is only loosely tied to this tool, plus a stray double period. Valid content, but not tight.

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?

With an output schema present, the description need not explain return values, and it does cover safety/billing/idempotency behavior well. However, for a tool with 26 parameters and zero schema descriptions, the near-total absence of parameter guidance leaves the definition incomplete for correct invocation.

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?

The description touches a few parameters indirectly by naming defaults (90-day lookback, DISPLAY evidence) and explaining forceRefresh reuse, and it mentions idempotencyKey. But the schema has 26 parameters with 0% description coverage, and the vast majority (evidenceMode, strategyMode, seat/advertiser identifiers, competitor fields, recommendationMode) are undocumented in both schema and description, so it fails to compensate for the coverage gap.

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?

States a specific verb and resource: run canonical LeanrIQ Competitor Intelligence V2 for one advertiser-scoped competitor, and identifies itself as a deprecated alias for run_competitor_intelligence. An agent can distinguish it from the base intelligence tool, though the 'get_' prefix sits awkwardly against a tool that actually initiates work.

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 implies the agent should prefer run_competitor_intelligence by labeling itself 'Deprecated alias', and explains the forceRefresh reuse condition, but never explicitly says 'do not call this; call the canonical tool instead' or states when/when-not this variant applies. Usage is inferable rather than directed.

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?