Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Meta, Google, TikTok & LinkedIn Ad Pixel Spy

detect_ad_spend_pixels
Read-onlyIdempotent

Inspect domains for active paid ad pixels such as Meta, Google Ads/GTM, TikTok, LinkedIn, and Microsoft Clarity to identify live ad spend signals for B2B lead qualification.

Instructions

Detect active paid ad spend signals on any website including Meta Pixel, Google Ads/GTM, TikTok Pixel, LinkedIn Insight Tag, and Microsoft Clarity ($0.80/1k).

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": {
      "domains": "<domains>"
    },
    "name": "detect_ad_spend_pixels"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesDomains to inspect for active ad pixels

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.4/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 genuinely new context in the form of unit pricing ($0.80/1k), but says nothing about detection methodology, false-positive behavior, or what 'active' means, so credit is moderate.

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?

A single front-loaded sentence naming the capability, coverage, and price with no filler. Efficient and scannable, though the long list of pixel vendors makes it slightly dense.

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 read-only detection tool with no output schema, an agent still lacks any sense of the return shape (which pixels were found, per-domain structure, confidence signals). Annotations cover safety and the single parameter is fully documented, but the result contract is left entirely implicit.

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?

Only one parameter exists and the schema already describes it at 100% coverage ('Domains to inspect for active ad pixels'). The description's phrase 'on any website' reinforces that arbitrary domains are accepted but adds no format, batching, or limit semantics beyond the schema. 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 ('Detect') and resource ('active paid ad spend signals on any website'), then enumerates the exact pixel types it covers (Meta, Google Ads/GTM, TikTok, LinkedIn Insight Tag, Microsoft Clarity). This is far more concrete than the title alone, though it does not explicitly contrast itself with neighboring spy/scrape tools, which is what keeps it from a 5.

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?

Usage is only implied by 'on any website' – the agent can infer this is for auditing domains for ad-tech presence, but there is no explicit when-to-use, when-not-to-use, or named alternative among the many sibling spy tools. Adequate but with clear gaps.

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