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.

run_competitor_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.. 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
```
AddedAug 13, 2026

TDQS

A3.5/5.0

Behavior5/5

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

Annotations only cover readOnly/idempotent/destructive/openWorld, but the description adds billable-AI-usage classification, durable execution, optional task support, the three mutation modes, and a partial-failure policy ("completed_items_not_rolled_back") that tells the agent what is NOT undone on failure. The idempotency-key derivation note also explains retry behavior concretely, well beyond what the annotations convey.

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 purpose is properly front-loaded and the behavioral metadata is informative, but the block is dense boilerplate that repeats the title verbatim and includes generic output-style guidance likely shared across tools. There is also a doubled period ("available.."), a minor polish issue.

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-value explanation is not required, and the assistantSummary/raw-JSON guidance is a useful addition. But for a 37-parameter, zero-required tool with nested objects, the description leaves an agent unable to tell which identity and scoping parameters to supply, which is a meaningful completeness gap.

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 37 parameters, so the description carries the full burden — and it only clarifies two of them (forceRefresh reuse semantics and the 90-day DISPLAY evidence default). Nothing explains how to identify the target competitor (competitorId vs competitorDomain vs competitorName/website), which market/region/markets fields to use, or what locales, strategyModes, or recommendationMode mean.

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 ("Run canonical LeanrIQ Competitor Intelligence V2") and a precise scope ("one advertiser-scoped competitor"), which is distinguishable from the read-style sibling get_competitor_intelligence. However, it never explicitly names that sibling or explains the run-vs-get relationship, so the differentiation is inferred rather than stated.

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 gives one real usage cue: "Without forceRefresh, an existing canonical result is reused when available," which tells the agent when regeneration is needed. But it never names alternatives (get_competitor_intelligence, list_competitor_evidence, leanriq_get_competitor_creative_intelligence) or states when to pick this tool over them, and the listed mutation modes (validate_only, preview_only, execute) come with no guidance on when to use each.

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?