Skip to main content
Glama

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. (deprecated alias)

leanriq_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.. Deprecated alias for get_brand_visuals. 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "advertiserId": "<advertiserId>",
      "brandName": "<brandName>",
      "websiteUrl": "<websiteUrl>"
    },
    "name": "leanriq_get_brand_visuals"
  }
}

Input Schema

NameRequiredDescriptionDefault
seatIdNo
optionsNo
storageNo
seatNameNo
brandNameYes
websiteUrlYes
advertiserIdYes
sourceLocaleNo
targetMarketNo
contentLocaleNo
marketContextNo
targetMarketsNo
contentLocalesNo
defaultContentLocaleNo
marketLanguageProfileNo
resolvedContentLocaleNo
languageVariantGroupIdNo
requestedOutputLocalesNo
supportedContentLocalesNo

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes
errorNo
statusYes
assistantSummaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / options / properties / socialLookbackMonths
      Added value: +{
      +  "default": 3,
      +  "maximum": 3,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. Changed12 schema fields changed
    • 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"
      +}
  3. Changed2 schema fields changed
    • changedInput schema / properties / options / properties / maxImages / default
      Previous value: -30New value: +60
    • changedInput schema / properties / options / properties / maxSocialImages / default
      Previous value: -10New value: +30
  4. Changed3 schema fields changed
    • 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"
      +}
  5. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, and the description largely restates this ("Classification: read-only") while adding two non-annotation facts: execution is synchronous and task support is forbidden. The genuinely useful behavioral disclosure is that it "does not save to Studio," but nothing is said about the external scraping/browser behavior implied by openWorldHint or about rate limits and latency of a fetch that scrapes a site.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence duplicates the title verbatim, and the segment ends with a doubled period ("does not save to Studio.."), signalling unedited concatenation. The remaining half is generic orchestration boilerplate ("Never display raw JSON... Mention IDs only when useful") that is not front-loaded and dilutes the two sentences that actually matter.

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 legitimately omitted, and deprecation status is disclosed. But for a 19-parameter, nested, network-scraping read tool, the definition omits all parameter guidance and gives no instruction on how the deprecated alias should be handled relative to its replacement — the two things an agent most needs here.

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?

There are 19 parameters with 0% schema description coverage, including a deeply nested `options` object with 19 sub-fields and a `storage` object, yet the description says nothing about any of them. The list of visual asset types loosely hints at fetchLogos/fetchImages/extractColours/fetchFonts, but it never indicates these are toggleable options, never explains the required advertiserId/brandName/websiteUrl triple, and never mentions caps or defaults.

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 description gives a concrete verb-plus-resource statement ("Collect brand logos, imagery, colours, fonts, and visual previews") and explicitly identifies itself as a "Deprecated alias for get_brand_visuals," which distinguishes it from refresh_brand_visuals and the canonical get_brand_visuals. The first sentence is a near-verbatim repeat of the title, so it earns clarity mainly through the deprecation note rather than original wording.

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 states a usable trigger: "Use this before build_ad when a campaign needs visual grounding." However, it never tells the agent what to do about the deprecation — it names get_brand_visuals as the canonical tool but does not say "call that instead," leaving the routing decision to inference. No when-not-to-use condition is stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources