Social Fetch

List Google company ads

google_company_ads_list

Read-only

List ads a company or advertiser is running in Google Ad Transparency. Accepts a domain or advertiser id. Returns a list (use cursor when paginated).

Input Schema

TableJSON Schema

Name	Required	Description
`trim`	No	Ignored if this tool does not support it.
`limit`	No	Ignored if this tool does not support it.
`topic`	No	Optional topic filter. When `political`, `region` is required.
`cursor`	No	Opaque pagination cursor from a previous response.
`domain`	No	Company domain when you do not have an advertiser id.
`format`	No	Optional creative format filter.
`offset`	No	Ignored if this tool does not support it.
`region`	No	Optional region filter as a two-letter country code.
`context`	Yes	Describe the user's underlying goal in one sentence — not the tool you are calling.
`endDate`	No	Optional end date filter in YYYY-MM-DD format.
`pageSize`	No	Ignored if this tool does not support it.
`platform`	No	Optional Google surface filter.
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`startDate`	No	Optional start date filter in YYYY-MM-DD format.
`maxResults`	No	Ignored if this tool does not support it.
`max_results`	No	Ignored if this tool does not support it.
`advertiserId`	No	Google Ad Transparency advertiser id when you have it instead of a domain.
`conversation_id`	No	Echo 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.

Changed6 schema fields changedSep 21, 2026

addedInput schema / properties / limit

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / maxResults

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / max_results

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / offset

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / pageSize

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / trim

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

Changed5 schema fields changedSep 5, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Describe the user's underlying goal in one sentence — not the tool you are calling.",
+  "type": "string"
+}

addedInput schema / properties / conversation_id

Added value: +{
+  "description": "Echo 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.",
+  "type": "string"
+}

addedInput schema / properties / llm_model

Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}

addedInput schema / required

Added value: +[
+  "context",
+  "llm_model"
+]

Changed1 schema field changedAug 27, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed1 schema field changedJul 29, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed1 schema field changedJul 29, 2026

changedInput schema / properties / cursor / description

Previous value: -"Opaque pagination cursor from a previous response (`data.page.nextCursor`)."New value: +"Opaque pagination cursor from a previous response."

First observedJul 20, 2026

TDQS

A4/5.0

Behavior4/5

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

readOnlyHint=true and openWorldHint=true already carry the safety profile. The description adds genuine behavioral value beyond annotations by stating that the tool returns a list and explicitly instructs to use a cursor when results are paginated. It does not discuss rate limits or scoping, but for a safe read-only list tool this is meaningful coverage.

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

Conciseness5/5

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

Three short sentences with no waste: the core action comes first, then the lookup inputs, then the pagination note. It avoids repeating schema content and front-loads the information most important for tool selection.

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?

For a read-only list tool with full schema coverage, the description covers the essential call pattern: what is listed, how to identify the company (domain or advertiser id), and pagination behavior. It could be more explicit about choosing between domain and advertiserId and about filter interactions like political requiring region, but the schema already states those, so the gap is minor.

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 all 18 parameters are already documented in the schema. The description adds little beyond echoing that domain/advertiserId are the lookup keys and that cursor relates to pagination. With full schema coverage, the baseline of 3 is appropriate.

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?

Description uses a specific verb 'List' with a clear resource: ads a company or advertiser is running in Google Ad Transparency. It identifies the two supported lookup keys (domain or advertiser id), which distinguishes it from siblings like google_adLibrary_ad_get (single ad retrieval) and google_adLibrary_advertisers_search (advertiser lookup).

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 establishes the context — you use it to list ads run by a company/advertiser — but it gives no explicit when-to-use versus alternatives guidance. It does not point to google_adLibrary_ad_get for single ads or google_adLibrary_advertisers_search for finding an advertiser id, so the agent must infer routing from sibling names.

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

All Social Fetch 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.

List Google company ads

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources