Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Google company ads

google_company_ads_list
Read-onlyIdempotent

Lists the ads a company or advertiser is running in Google Ad Transparency, filtered by domain, advertiser ID, topic, region, dates, platform, or format. Use it to audit live ad creatives and targeting.

Instructions

List ads a company or advertiser is running in Google Ad Transparency. Optional inputs: domain, advertiserId, topic, region, startDate and 4 more. Returns a list (use cursor when paginated).

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "google_company_ads_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoOptional topic filter. When `political`, `region` is required.
cursorNoOpaque pagination cursor from a previous response.
domainNoCompany domain when you do not have an advertiser id.
formatNoOptional creative format filter.
regionNoOptional region filter as a two-letter country code.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
endDateNoOptional end date filter in YYYY-MM-DD format.
platformNoOptional Google surface filter.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
startDateNoOptional start date filter in YYYY-MM-DD format.
advertiserIdNoGoogle Ad Transparency advertiser id when you have it instead of a domain.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds pagination behavior ('use cursor when paginated'), which is useful, but says nothing about result volume, rate limits, or the required conversation_id sequencing.

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?

Two short sentences, front-loaded with the purpose. The 'and 4 more' shorthand is slightly lazy but keeps it compact; nothing is wasted.

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 12-parameter tool with no output schema, the description omits the non-obvious required parameters (context, llm_model) and the conversation_id sequencing rule, which are the most error-prone parts of invocation. Annotations cover safety, but the description leaves meaningful gaps.

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 description coverage is 100%, so every parameter is already documented in the schema. The description only enumerates parameter names ('domain, advertiserId, topic, region, startDate and 4 more') without adding meaning, so baseline 3 applies.

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 and resource: 'List ads a company or advertiser is running in Google Ad Transparency.' An agent can tell this is an ad-listing tool, though it does not explicitly contrast with siblings like google_adLibrary_ad_get or google_adLibrary_advertisers_search.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance, and no mention of alternatives. The only usage hint is 'use cursor when paginated,' which is a mechanical note rather than selection guidance.

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