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

TableJSON Schema

Name	Required	Description	Default
`seatId`	No
`options`	No
`storage`	No
`seatName`	No
`brandName`	Yes
`websiteUrl`	Yes
`advertiserId`	Yes

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.

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

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive safety, so the bar is lower, and the description adds useful context: synchronous execution, task support forbidden, and that it does not persist to Studio. It omits operational traits like scraping/browser-fetch latency, failures on unreachable URLs, or rate limits for the open-world fetch.

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 core purpose and routing sentence is front-loaded and tight, but the opening sentence duplicates the title verbatim and is followed by boilerplate classification lines and a long orchestration/presentation-policy paragraph. Roughly half the text is not about tool selection.

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 need not be described, and annotations carry the safety profile. However, for a tool with a 17-field options object, nested storage config, and zero schema documentation, the description leaves an agent unable to reason about how to configure the call.

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 7 parameters, and the nested options object exposes ~17 undocumented knobs (useBrowser, scrapeSocial, includeAiGeneratedImages, storage bucket/prefix/cdnBaseUrl) with no explanation of defaults or effects. The description contributes no parameter meaning at all, leaving required advertiserId/brandName/websiteUrl and all option flags unexplained.

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

Purpose5/5

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

States a specific verb (collect) and resources (logos, imagery, colours, fonts, visual previews) plus the downstream consumer (Studio creative builds). An agent can distinguish it from get_brand_profile and refresh_brand_visuals from the description alone.

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?

Gives explicit timing ('Use this before build_ad when a campaign needs visual grounding') and a negative constraint ('does not save to Studio'). It does not name the obvious alternative, refresh_brand_visuals, or say when refresh is preferable.

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?