Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Google Ad Library ad

google_adLibrary_ad_get
Read-onlyIdempotent

Fetch a single Google Ad Transparency creative by its public Ad Transparency URL. Use it to pull advertiser ad details for research or verification.

Instructions

Get a single Google Ad Transparency creative by public Ad Transparency URL. Requires url.

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

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Public Google Ad Transparency URL for the creative.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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.
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

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds only that the URL must be public; it says nothing about rate limits, quota, auth needs, or error behavior, and the sequencing rule for conversation_id is left entirely to the schema.

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?

Two short sentences, zero waste, with the resource and the required lookup key front-loaded. Nothing superfluous to trim.

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 single-item read, the description plus annotations are close to sufficient, but with no output schema the agent gets no sense of what the returned creative contains or whether the response includes the conversation_id envelope the tool requires on subsequent calls.

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 the schema already documents url, context, llm_model and conversation_id in detail. The description merely restates that url is required, adding no format hints or examples beyond the schema's own "Public Google Ad Transparency URL for the creative."

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?

Specific verb and resource ("Get a single Google Ad Transparency creative") plus the lookup key ("by public Ad Transparency URL"), which cleanly separates it from the search-style siblings such as google_adLibrary_advertisers_search and the per-platform *_ad_get tools.

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 phrase "by public Ad Transparency URL" implies this is a detail fetch that follows a search, but it never states that explicitly, never says when to pick it over a search sibling, and gives no prerequisites or failure conditions (e.g., what happens with a non-public or malformed URL).

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