Skip to main content
Glama

Social Fetch

by io.github.social-freak-ltd

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
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.
endDateNoOptional end date filter in YYYY-MM-DD format.
platformNoOptional Google surface filter.
startDateNoOptional start date filter in YYYY-MM-DD format.
advertiserIdNoGoogle Ad Transparency advertiser id when you have it instead of a domain.

TDQS

A3.7/5.0
Behavior3/5

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

The description adds behavioral notes about pagination via cursor and that it returns a list, which complements the readOnlyHint and openWorldHint annotations. It does not contradict the annotations, but it does not disclose rate limits, authentication, or return structure details.

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?

The description is two sentences with zero waste: the core purpose is front-loaded, and the essential details (domain/advertiser id, cursor pagination) are conveyed without redundancy.

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?

Given the large number of optional parameters (9) and the absence of an output schema, the description is minimal. It does not mention the available filters (topic, region, platform, dates) though these are documented in the schema, and it does not describe the returned list's contents beyond being a list. Adequate but could be more helpful.

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?

The schema covers 100% of parameters with descriptions. The description reinforces the primary choice between domain and advertiserId and mentions cursor usage, but it does not add meaning beyond what the schema already documents for each parameter.

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 'List' and resource 'ads' within 'Google Ad Transparency', and clarifies it accepts a domain or advertiser id. This clearly distinguishes it from sibling tools like google_adLibrary_ad_get (single ad) and google_adLibrary_advertisers_search (advertiser search).

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 implies usage when you have a company domain or advertiser id, but it does not explicitly mention alternatives or when not to use this tool. It lacks exclusions or comparison to related Google ad tools, so guidance is left to inference.

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

All Social Fetch toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation5/5

Each tool is clearly scoped to a specific platform and action (e.g., facebook_post_get vs instagram_post_get). Descriptions explicitly differentiate similar tools across platforms, and within-a-platform tools like tiktok_search_videos_list vs tiktok_search_hashtag_list have clear disambiguation notes.

Naming Consistency5/5

All 167 tools follow a strict `platform_resource_action` pattern (e.g., youtube_video_comments_list). No mixing of styles—snake_case throughout, with consistent verb ordering (get, list, search, etc.).

Tool Count2/5

The server has 167 tools, which is far beyond the typical well-scoped range of 3-15. While the broad multi-platform scope justifies many tools, this extreme number makes the tool surface overwhelming and difficult for an agent to navigate efficiently.

Completeness4/5

The tool set covers a wide range of platforms and operations including profile retrieval, post/video fetching, comments, search, transcripts, and ad library access. Minor gaps exist (e.g., no Facebook events or LinkedIn messaging), but the surface is comprehensive for a read-only data aggregation use case.

Resources