Skip to main content
Glama

refresh brand visuals

refresh_brand_visuals
Idempotent

refresh brand visuals. Classification: writes to Studio, 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. For a mutation when more than one seat is authorised, seatId or seatName must be supplied on that exact tool call; a remembered or previously selected seat is not sufficient for a write.

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>",
      "accountId": "<accountId>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "refresh_brand_visuals"
  }
}

Input Schema

NameRequiredDescriptionDefault
seatIdNo
optionsNo
storageNo
seatNameNo
accountIdYes
brandNameYes
websiteUrlYes
advertiserIdYes
sourceLocaleNo
targetMarketNo
contentLocaleNo
marketContextNo
targetMarketsNo
contentLocalesNo
idempotencyKeyYes
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

C2.5/5.0
Behavior4/5

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

Beyond the annotations, the description discloses genuinely load-bearing behavior: the call is billable AI usage, execution is durable, and the partial-failure policy is 'completed_items_not_rolled_back' — meaning a failed run leaves artifacts behind, which an agent must know before retrying. It also explains how a missing idempotencyKey is derived deterministically and that a seat must be supplied on the exact write call rather than remembered. The one gap is that it never says what the refresh actually produces or how long it takes.

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 metadata labels (Classification, Execution, Task support, Mutation modes, Partial failure policy) are terse and front-loaded, which is good. However, a large block of response-formatting boilerplate ('Never display raw JSON', 'Mention IDs only when useful', 'suggest the next best LeanrIQ action') is generic presentation policy rather than tool-specific guidance, and it dilutes the sections that matter.

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?

An output schema exists, so return values need not be described, and the mutation-safety story is well covered. But for a 21-parameter, nested-object mutation with zero schema descriptions, the definition leaves an agent unable to choose values for 'options', 'storage', 'targetMarket'/'targetMarkets', or the locale fields — the biggest source of misuse risk 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?

Schema description coverage is 0% across 21 parameters, including a large nested 'options' object (maxFonts, fetchLogos, useBrowser, scrapeSocial, socialLookbackMonths, etc.) and 'storage'/'marketContext' objects that get no explanation at all. The description only adds meaning for two parameters — idempotencyKey (auto-derived retry key) and seatId/seatName (mandatory per-call when multiple seats are authorised) — leaving the rest entirely undocumented.

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 opening sentence 'refresh brand visuals' is a restatement of the tool name and title, not an explanation of the operation. The only concrete additions are effect labels ('writes to Studio, creates billable AI usage'), which describe consequences rather than what is actually refreshed (fonts, logos, images, colours, CTAs). Nothing distinguishes it from siblings like refresh_brand_profile or get_brand_visuals.

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 'Mutation modes: validate_only, preview_only, execute' line hints at a safe dry-run workflow, but the description never states when to call this tool versus refresh_brand_profile or get_brand_visuals. There are no prerequisites (e.g. advertiser must exist, website must be reachable) and no explicit exclusions.

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