Skip to main content
Glama

get_ad_attributes

Read-onlyIdempotent

List an ad's OUTPUT attributes and how each is currently sourced — the tool for SOLVING THE ATTRIBUTE FORM (the discipline users struggle with). Use this to find required ad attributes that are still unmapped. Returns {integrationId, attributes:[{code, label, required, hidden, valueSource, platformCode, constant, composedValue, defaultPlatformCode, defaultConstant, allowedValues, formatType, ruleId, ruleName, ruleEnabled, priceAttribute, currency, currencyConversionEnabled, configured, stepField}], requiredCount, requiredUnmappedCount, unresolvedCodes}. valueSource is rule|composed|attribute|constant|unmapped (the effective source; a rule attached but ruleEnabled=false does NOT count and the attribute reads 'unmapped'). priceAttribute=true marks a money attribute (formatType price / price_with_delete); currency is its target currency and currencyConversionEnabled whether Koongo converts the value into it (null = not a price attribute). Conversion only matters when the price is in a DIFFERENT currency than the store; if the attribute's name already names a currency (e.g. its label/code contains "EUR") the value is ALREADY in that currency, so set currencyConversionEnabled=false to avoid converting it twice. requiredUnmappedCount is the running count of REQUIRED attributes with no working source — 0 means the form is solved and the ad can build/export; unresolvedCodes lists exactly which ones to fix. Pass only_unresolved:true to get just those rows. To fill one, match the user's attribute label to its code, then map_ad_attribute. ad_id is from Each row also says WHERE its value comes from: configured=true is a mapping of the customer's own, stepField names a wizard form step field that drives it (change it there with configure_ad_step — mapping it here writes an override that beats the step for good), and neither means the value is only the channel definition's default. A default is not a decision: check it against the store's data before trusting it. list_ads. project_id is OPTIONAL (project_id_required otherwise — then call list_projects). IF categoryAttributeWarmup IS PRESENT WITH pending:true THIS LIST IS INCOMPLETE: the channel's category-specific attributes are still downloading, so requiredUnmappedCount and unresolvedCodes are PROVISIONAL — a required attribute that is not in the list yet cannot be counted as unmapped, so the form can look solved when it is not. Poll ad_status until the block is absent or state is 'ready', then read this again before mapping.

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": {
      "ad_id": "<ad_id>"
    },
    "name": "get_ad_attributes"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_idYes
project_idNo
only_unresolvedNoReturn only REQUIRED attributes that still have no working value source.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, it discloses important interpretation rules and failure modes: disabled rules leave attributes unmapped, defaults are not customer decisions, wizard mappings can be permanently overridden, and warmup can make counts appear complete when they are provisional. The currency-conversion guidance also addresses a concrete double-conversion risk.

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 purpose is front-loaded, but the definition is excessively long and dense, with a large inline return-field dump, frequent all-caps emphasis, and several nested parenthetical explanations. The misplaced ad_id/list_ads sentence further disrupts the structure, even though much of the detailed content is operationally useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description supplies the return shape and explains the fields most important to correct decisions, including valueSource, provenance, price handling, unresolved counts, and provisional warmup results. Combined with parameter discovery and concrete next-step tools, it provides unusually complete context for invoking the tool and acting on its response.

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

Parameters4/5

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

The description compensates well for 33% schema coverage by explaining only_unresolved, the optional project_id and its project_id_required/list_projects fallback, and the intended ad_id provenance. However, the ad_id guidance is corrupted into 'ad_id is from ... list_ads' around an intervening paragraph, making that parameter explanation unnecessarily difficult to parse.

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?

The opening precisely states that the tool lists an ad's output attributes and their current value sources, with a specific focus on finding required attributes that remain unmapped. This clearly distinguishes it from sibling tools that retrieve general ad details, map attributes, or configure wizard steps.

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

Usage Guidelines5/5

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

It gives an explicit workflow: inspect unresolved attributes, optionally filter with only_unresolved, match labels to codes, and call map_ad_attribute. It also routes step-driven values to configure_ad_step and explains when to poll ad_status and reread the list before mapping because category attributes are still downloading.

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