A2A Retailmedia — the agentic retail-media hub for grocery

List Banners

list_banners

Read-onlyIdempotent

Pick the banners: the grocery banners of one market with each one's media program (or "none listed") and card status. with_program=true returns only banners with a program listed.

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": {
      "market": "<market>"
    },
    "name": "list_banners"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`market`	Yes
`offset`	No
`search`	No
`with_program`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 11, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedOutput schema / additionalProperties
```
Removed value: -true
```
First observedOct 5, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare this a safe, idempotent, non-destructive, closed read, so the safety profile is fully covered elsewhere. The description usefully adds that a banner without a program shows 'none listed' and that with_program filters on that, but it says nothing about pagination behavior or the meaning of limit/offset.

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?

Two sentences, no obvious fluff, and the filter rule is placed at the end where it is easy to miss. The run-on phrasing of the first sentence ('Pick the banners: the grocery banners of...') is awkward and slightly obscures the core action.

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 spelled out, and annotations cover safety. However, for a 5-parameter tool with zero schema coverage, leaving three parameters unexplained means the definition is not quite complete enough for an agent to call it fully 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?

Schema description coverage is 0%, so the description must carry the parameter burden. It clarifies 'market' and 'with_program' but leaves limit, offset, and search entirely undocumented in both schema and description, which is a substantial gap for a 5-parameter tool.

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?

States a specific verb (list/pick) and resource (grocery banners of one market), plus what each entry carries (media program, card status). It does not distinguish itself from sibling list_banner_cards or get_banner_card, so it falls short of full sibling differentiation.

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?

The description gives one concrete usage rule: setting with_program=true returns only banners that have a program listed. Beyond that there is no guidance on when to choose this over list_banner_cards or get_banner_card, and no prerequisites are stated.

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

All A2A Retailmedia — the agentic retail-media hub for grocery 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.