Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Google Ads Transparency & Competitor Ad Pixel Spy

scrape_google_ads_transparency
Read-onlyIdempotent

Audit competitor domains or niche keywords to uncover Google Ads Transparency URLs, conversion IDs, GTM tags, tracking pixels, ads.txt sellers, and marketing contacts.

Instructions

Audit competitor domains or niches for Google Ads Transparency URLs, Google Ads Conversion IDs (AW-), GTM tags, Meta/LinkedIn/TikTok pixels, ads.txt sellers, and marketing contacts ($0.75/1k).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scrape_google_ads_transparency"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsNoCompetitor or advertiser domains, e.g. ["monday.com", "clickup.com"]
queriesNoOptional niche keywords to discover active advertisers
maxItemsNoMaximum advertiser records

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds context the annotations don't: it discloses the cost model ($0.75/1k) and enumerates the data categories returned, which is meaningful for a paid, no-output-schema tool. It still doesn't mention rate limits or failure behavior for unreachable domains.

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?

One dense sentence with the action front-loaded and the extraction targets listed after it; nothing is wasted. The parenthetical pricing is compact and useful rather than noise.

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?

With no output schema, the description compensates by naming the exact fields the agent should expect back, which is the main thing an agent needs. It is slightly incomplete on the interaction of the optional domains/queries inputs and on the cost calculation basis, but it is adequate for a 3-parameter read-only scraper.

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% with three documented parameters, so the schema already carries the semantics. The description only loosely maps 'domains or niches' onto the domains/queries parameters and says nothing about maxItems or how domain and query inputs combine, so it adds little beyond the structured fields.

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 description gives a specific verb ('Audit') plus a resource ('competitor domains or niches') and enumerates exactly what it extracts: Transparency URLs, AW- conversion IDs, GTM tags, pixels, ads.txt sellers and contacts. An agent knows precisely what the tool returns, though it never names or contrasts a sibling such as detect_ad_spend_pixels, which appears to overlap.

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 'Audit competitor domains or niches' implies the usage context (competitor/competitive-intel research) and the choice between passing domains versus niche queries. However, there is no explicit when-to-use vs when-not guidance and no mention of alternatives for overlapping pixel/ad-spend detection, so selection still requires inference.

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