Skip to main content
Glama

Visibility Genies

Find advertisers

find_ad_advertisers

Finds the advertisers Google's Ads Transparency Center lists under a name or domain, in the project's country, with each one's advertiserId and approximate ad count. Pass an advertiserId (or a domain) to get_competitor_ads. Queued at normal priority: a 'processing' answer means call again with the same arguments in 2-3 minutes, at no extra cost. Estimated price: $0.01 a search. Each call may spend up to the workspace's agent spend limit ($2.00 unless changed in Settings) without asking: it holds at most its estimate plus a margin while it runs and is charged what it bought, never more. A call whose maximum is above the limit is refused before anything is bought, with its estimate and maximum: ask the user, then call again with approvedMaxCostUsd set to the amount they approved.

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": {
      "projectId": "<projectId>",
      "query": "<query>"
    },
    "name": "find_ad_advertisers"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesAn advertiser's name or a domain to look up in Google's Ads Transparency Center.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
approvedMaxCostUsdNoThe most, in USD, the user approved for this call after seeing its estimate and maximum. Only needed after a call was refused for costing more than the workspace's agent spend limit; never set it without asking the user.

Output Schema

NameRequiredDescriptionDefault
costNo
metaNo
statusYes
advertisersNo
savedResultIdNo

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?

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) by disclosing the asynchronous queue behavior, the exact retry protocol and that retries are free, the $0.01 estimate, the workspace spend limit default of $2.00, the hold-plus-margin charging model, and the refusal/approval path. That is precisely the cost and latency context an agent needs before invoking a paid, open-world lookup.

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?

Front-loaded with the purpose and sibling handoff, then cost/queue rules, then the refusal path — a sensible order. It is a single dense block rather than separated lines, so the pricing and approval sentences take some parsing, but every sentence carries operational information rather than filler.

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?

For a paid, queued, open-world lookup with an output schema already covering return shape, the description supplies everything else an agent needs: cost, spend ceiling, charging semantics, retry timing, and the escalation path when a call is refused. Nothing material is left for the agent to guess.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds workflow meaning the schema only implies: it explains what a 'processing' answer means for a repeat call and frames approvedMaxCostUsd as a post-refusal, user-approval-only parameter passed as the amount they approved. The projectId/query semantics are left entirely to the schema, which already documents them well.

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?

States a specific verb and resource ('Finds the advertisers Google's Ads Transparency Center lists under a name or domain') plus the scope constraint ('in the project's country') and what each result carries ('advertiserId and approximate ad count'). An agent can distinguish this from sibling lookups like find_serp_competitors without opening the schema.

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?

Gives an explicit downstream handoff ('Pass an advertiserId (or a domain) to get_competitor_ads') and the retry rule for 'processing' answers. It does not state when to prefer a different find_* sibling or when a domain lookup is better than a name lookup, so it stops short of full alternative routing.

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