LeanrIQ

Collect brand logos, imagery, colours, fonts, and visual previews for use in Studio creative builds. Use this before build_ad when a campaign needs visual grounding; this read capability does not save to Studio.

get_brand_visuals

Read-onlyIdempotent

Collect brand logos, imagery, colours, fonts, and visual previews for use in Studio creative builds. Use this before build_ad when a campaign needs visual grounding; this read capability does not save to Studio.. 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	Default
`seatId`	No
`options`	No
`storage`	No
`seatName`	No
`brandName`	Yes
`websiteUrl`	Yes
`advertiserId`	Yes
`sourceLocale`	No
`targetMarket`	No
`contentLocale`	No
`marketContext`	No
`targetMarkets`	No
`contentLocales`	No
`defaultContentLocale`	No
`marketLanguageProfile`	No
`resolvedContentLocale`	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.

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

addedInput schema / properties / targetMarkets

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

Changed2 schema fields changedOct 5, 2026
- changedInput schema / properties / options / properties / maxImages / default
```
Previous value: -30New value: +60
```
- changedInput schema / properties / options / properties / maxSocialImages / default
```
Previous value: -10New value: +30
```

Changed3 schema fields changedSep 2, 2026

addedInput schema / properties / options / properties / fetchVideos
```
Added value: +{
+  "default": true,
+  "type": "boolean"
+}
```

addedInput schema / properties / options / properties / maxSocialImages

Added value: +{
+  "default": 10,
+  "maximum": 40,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / options / properties / maxVideos

Added value: +{
+  "default": 12,
+  "maximum": 30,
+  "minimum": 0,
+  "type": "integer"
+}

First observedAug 12, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, so the 'Classification: read-only' line is largely redundant, but the description adds genuinely new traits: synchronous execution, task support forbidden, and an explicit side-effect statement ('does not save to Studio'). The output-handling rules (assistantSummary first, don't dump raw JSON) usefully shape agent behavior beyond the 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 purpose is correctly front-loaded, but the body is generic orchestration boilerplate that repeats across tools and a stray double period ('Studio..') signals unpolished text. The generic output-display rules take up roughly half the description for one repeated instruction.

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?

The output schema means return values need not be described, and the read-only/no-persist behavior is covered. But for a 19-parameter tool with deep nested option objects, storage config, and locale/market context, the near-total absence of parameter and configuration guidance leaves the agent under-equipped to invoke it correctly.

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?

19 parameters with 0% schema description coverage and no parameter guidance anywhere in the description: required fields (advertiserId, brandName, websiteUrl) and the nested options/storage/marketContext objects are entirely unexplained. At most, listing 'logos, imagery, colours, fonts' loosely maps to the fetch/extract toggles, which is far too thin for a schema this large.

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 opening sentence gives a specific verb ('Collect') and concrete resources (logos, imagery, colours, fonts, previews) plus the target consumer ('Studio creative builds'). However, it never distinguishes itself from close siblings like get_brand_profile or refresh_brand_visuals, which an agent must choose between.

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

Usage Guidelines4/5

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

It gives explicit timing ('Use this before build_ad when a campaign needs visual grounding') and a key constraint ('this read capability does not save to Studio'), which implies refresh_brand_visuals is the persisting counterpart. It stops short of naming that alternative or stating when-not to use this tool, so it is clear context rather than full routing guidance.

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?