LeanrIQ

get vertical intelligence

get_vertical_intelligence

Read-onlyIdempotent

get vertical intelligence. Classification: read-only. Execution: synchronous. Task support: forbidden. 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.

Input Schema

Name	Required	Description
`brief`	No
`force`	No
`input`	No
`assets`	No
`prompt`	No
`seatId`	No
`taskId`	No
`assetId`	No
`outputs`	No	Optional editable/static JPEG/PNG delivery requirements. Studio persistence is required for static output.
`audience`	No
`campaign`	No
`creative`	No
`flightId`	No
`seatName`	No
`template`	No
`accountId`	No
`objective`	No
`advertiser`	No
`campaignId`	No
`creativeId`	No
`templateId`	No
`creativeIds`	No
`persistence`	No
`advertiserId`	No
`instructions`	No
`sourceLocale`	No
`targetMarket`	No
`contentLocale`	No
`marketContext`	No
`targetMarkets`	No
`contentLocales`	No
`idempotencyKey`	No
`requestedFormats`	No
`defaultContentLocale`	No
`marketLanguageProfile`	No
`resolvedContentLocale`	No
`skipTraffickedRebuild`	No
`languageVariantGroupId`	No
`requestedOutputLocales`	No
`supportedContentLocales`	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.

Changed13 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 / outputs

Added value: +{
+  "description": "Optional editable/static JPEG/PNG delivery requirements. Studio persistence is required for static output.",
+  "items": {
+    "anyOf": [
+      {
+        "additionalProperties": false,
+        "properties": {
+          "type": {
+            "const": "editable",
+            "type": "string"
+          }
+        },
+        "required": [
+          "type"
+        ],
+        "type": "object"
+      },
+      {
+        "additionalProperties": false,
+        "properties": {
+          "format": {
+            "enum": [
+              "jpeg",
+              "png"
+            ],
+            "type": "string"
+          },
+          "maxBytes": {
+            "exclusiveMinimum": 0,
+            "maximum": 9007199254740991,
+            "type": "integer"
+          },
+          "quality": {
+            "maximum": 100,
+            "minimum": 1,
+            "type": "integer"
+          },
+          "type": {
+            "const": "static",
+            "type": "string"
+          }
+        },
+        "required": [
+          "type"
+        ],
+        "type": "object"
+      },
+      {
+        "enum": [
+          "editable",
+          "static_jpeg",
+          "static_png"
+        ],
+        "type": "string"
+      }
+    ]
+  },
+  "maxItems": 8,
+  "type": "array"
+}

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"
+}

addedInput schema / properties / targetMarkets

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

First observedAug 12, 2026

TDQS

C2.2/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, and the description's 'Classification: read-only' merely repeats that. It does add genuinely new behavioral context, though: the response is internal application state meant for orchestration, 'Task support: forbidden', and explicit rules against surfacing raw JSON/meta to the user. It says nothing about auth, rate limits, or data freshness.

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 first sentence is pure tautology, and the bulk of the text is response-formatting instruction that reads like a system prompt rather than tool documentation. It is front-loaded with classification facts but spends its length on output-handling rather than on what the tool does.

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?

With an output schema present the return shape needn't be described, but for a tool with 40 mostly-undocumented parameters and an unexplained purpose, the description is far from complete. An agent still cannot determine what inputs are needed or what this tool is for beyond the name.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are 40 parameters at only 3% schema description coverage, so the description must carry the burden of explaining them, and it explains none. Opaque fields like brief, input, assets, template, campaign, force, seatId, and persistence are left entirely undefined in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens by restating the tool name ('get vertical intelligence') and never explains what 'vertical intelligence' actually is or what resource it retrieves. It does not distinguish this tool from near-name siblings like get_world_intelligence, get_creative_intelligence, or get_competitor_intelligence, so an agent cannot tell when this specific tool is the right one.

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

Usage Guidelines2/5

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

The guidance present ('Use assistantSummary first', 'Never display raw JSON', 'suggest the next best LeanrIQ action') concerns how to present output, not when to invoke this tool versus alternatives. There is no statement of the trigger condition, prerequisites, or which sibling to prefer for a related need.

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?