Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

google_adLibrary_advertisers_search

Search Google's Ad Transparency Library for advertisers by name and optional region to retrieve advertiser IDs for ad research and verification.

Instructions

googleAdLibrary: Advertiser Search. GET /v1/google/adLibrary/advertisers/search. Search the Google Ad Transparency Library for advertisers to get their advertiser id. Pass region for non-US advertisers, like AU or CA. Costs 1 credit when it succeeds. Costs 1 credit when websites is not empty. Costs 1 credit when advertisers is not empty. Costs 0 credits when advertisers is empty. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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

Input Schema

NameRequiredDescriptionDefault
queryYesThe query to search for
regionNo2-letter country code to search in. Defaults to US when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose an unusually detailed credit-cost model including that errors, blocked/timed-out, invalid requests and cache hits are free. However, it omits authentication requirements, pagination/result limits, and return shape, and its cost clauses reference 'websites' and 'advertisers' being non-empty even though neither is an input parameter, which invites confusion about whether these are inputs.

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?

Purpose and region guidance are front-loaded and easy to scan, but more than half the text is a repetitive, partly self-tensioned cost block ('costs 1 credit when it succeeds' vs 'costs 0 credits when advertisers is empty') plus a closing sentence deferring to 'that operation's published cost' that resolves nothing.

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?

For a simple two-parameter search with no output schema, the description covers purpose, region usage and cost, but leaves the agent guessing about what the response contains beyond an advertiser id, whether results are paged or capped, and how failures surface. The cost wording is present but its referents ('websites', 'advertisers') are not defined for this tool.

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 baseline is 3; the schema already documents both query and region, including the US default. The description's region hint adds concrete country examples (AU, CA) but largely restates the schema's own default behavior, and it adds nothing about query semantics such as matching behavior or result caps.

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?

The first sentence names a specific verb and resource ('Search the Google Ad Transparency Library for advertisers') and states the output goal ('to get their advertiser id'), which implicitly positions it as the lookup step that feeds an id-based sibling such as google_company_ads. It stops short of naming any alternative tool, so the differentiation is inferred rather than stated.

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 only conditional guidance is for the region parameter ('Pass region for non-US advertisers, like AU or CA'), which is helpful but parameter-level, not tool-level. There is no statement of when to prefer this advertiser lookup over related ad-library searches (e.g., facebook_adLibrary_search_companies).

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

Deploy Server

Other Tools