Skip to main content
Glama

Show selected ads

show_ad_gallery
Read-onlyIdempotent

Displays up to 12 chosen ads as one visual gallery in clients that render MCP Apps widgets, and returns the same ads' data, image previews and links for text-only clients. For presenting the ads the user should see, once the relevant results are chosen. Each ad id is checked again for access; ads no longer available are left out with incomplete: true. A successful call does not prove that a gallery rendered.

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_ids": "<ad_ids>"
    },
    "name": "show_ad_gallery"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional search phrase these ads came from. Context only; no search is run.
ad_idsYes1 to 12 ad ids from search or list results; in text-only results, the final segment of each StealAds ad link.
response_formatNoOutput format: text (default) or json. table is not available for this tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / ad_ids / description
      Previous value: -"Ad IDs from search results; in text-only results use the final segment of the StealAds ad link."New value: +"1 to 12 ad ids from search or list results; in text-only results, the final segment of each StealAds ad link."
    • changedInput schema / properties / query / description
      Previous value: -"Words or advertiser name to search for."New value: +"Optional search phrase these ads came from. Context only; no search is run."
    • changedInput schema / properties / response_format / description
      Previous value: -"Output format: text or json for capped research examples; table is available only for tracked rival rows."New value: +"Output format: text (default) or json. table is not available for this tool."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses per-ad access re-validation and that unavailable ads are dropped with incomplete: true, which an agent could not infer from structured fields. The caveat that a successful call does not prove a gallery rendered is a genuinely useful behavioral warning that prevents false success reporting.

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

Conciseness4/5

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

Content is front-loaded with the two output modes and the 12-ad bound, and the caveat sentence is placed last where it lands as a warning. It is slightly dense in the opening sentence, but no sentence is filler.

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

Completeness4/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 carries the burden of describing returns and does so partially: the same ad data, image previews, links, and the incomplete: true marker. It does not describe the shape of the text/json/table payloads, but for a presentation-oriented tool with three simple parameters this is close to sufficient.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents all three parameters, including the 1-12 ad_ids range and the query/response_format meanings. The description reinforces the 12-ad cap and the id access-check behavior but adds no new syntax or format guidance beyond what the schema states, so the baseline 3 applies.

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 description states a specific verb and resource (displays chosen ads as a visual gallery) and enumerates both output modes: widget rendering for MCP Apps clients and raw data/image previews/links for text-only clients. It also bounds the scope (up to 12 ads), which distinguishes it from search/list tools and from single-ad retrieval.

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?

It gives a clear trigger: 'For presenting the ads the user should see, once the relevant results are chosen,' which implies use after a search or list call rather than instead of one. It does not explicitly name a sibling alternative or state when not to use it (e.g., single-ad inspection), so it falls short of a full when/when-not treatment.

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.