Skip to main content
Glama

Caelara Labs E-Commerce Intelligence

ad_pixel_detector

Detect ad, analytics and marketing pixels (Meta, TikTok, GA4, GTM, Pinterest, etc.) with tag IDs

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": "ad_pixel_detector"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage URL (or supply html)
htmlNoRaw HTML (or supply url)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses very little. It does not say whether the tool fetches the URL over the network, whether it executes JavaScript (so client-side-injected pixels are visible or not), whether results are static-only, or what the returned tag IDs look like. Only the vague 'with tag IDs' hints at output shape.

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 compact sentence with the core purpose front-loaded and no filler. The trailing 'with tag IDs' is slightly ambiguous as a dangling modifier, and the terseness leaves no room for the behavioral detail this tool otherwise lacks.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and a detection behavior that depends heavily on implementation details (network fetch, JS rendering, detection limits), the description is under-specified for correct invocation. An agent cannot predict cost, failure modes, or output structure from it. The simple two-parameter schema limits the damage, but the behavioral picture remains incomplete.

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 both parameters (url, html) are already documented as an either/or pair, and the baseline of 3 applies. The description adds nothing about parameter meaning beyond what the schema says, such as precedence when both are supplied or URL format expectations. This is acceptable but not additive.

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 names a specific verb ('Detect') and a concrete resource ('ad, analytics and marketing pixels'), lists well-known vendors (Meta, TikTok, GA4, GTM, Pinterest), and mentions that tag IDs are returned. An agent can tell this is a pixel-scanning tool rather than a product parser or validator. It does not explicitly contrast itself with the HTML-parsing siblings, so it falls just short of 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: the natural read is 'use this when you want to know which tracking pixels a page carries.' There is no explicit when-to-use statement, no mention of alternatives such as jsonld_product_parser or storefront_xray_composite, and no exclusions or prerequisites. Adequate but leaves routing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources