Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_ecom_ad_pixel_detector

Detect ad, analytics, and marketing pixels (Meta, TikTok, GA4, GTM, Pinterest) with their tag IDs by scanning a page URL or raw HTML, so you can verify which tracking tags are installed.

Instructions

[E-Commerce Intelligence] Detect ad, analytics and marketing pixels (Meta, TikTok, GA4, GTM, Pinterest, etc.) with tag IDs Measured p50 11 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://ecom.caelaralabs.com.

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": "caelara_ecom_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 observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the behavioral burden itself. It does add useful context beyond the name — stated latency percentiles, a dated benchmark source, the endpoint being called, and a hint that results include tag IDs — but it omits error behavior (e.g., neither url nor html supplied), whether both can be passed, and how results are structured or paginated.

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 sentences, purpose front-loaded, vendor examples and tag-ID hint included, then performance data. Nothing is repeated or padded relative to a simple two-parameter read tool.

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?

For a simple read-only detector with two optional parameters and no output schema, the description covers what is detected, where it runs, and roughly what comes back (tag IDs). The main remaining gap is failure handling when neither url nor html is provided, which an agent would benefit from knowing.

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 coverage is 100% and both parameters already carry descriptions that explain the url-or-html choice. The description adds nothing about parameter semantics on top of that, so the baseline of 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?

Uses a specific verb ("Detect") and names the resource precisely: ad, analytics and marketing pixels, with example vendors (Meta, TikTok, GA4, GTM, Pinterest). An agent can tell what it does, though it never distinguishes itself from the adjacent caelara_seo_serp_pixel_preview, which sounds related.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no conditions under which this tool is preferred over a sibling, and no note on when not to use it. Usage is only inferable from the purpose sentence, and the sibling pixel_preview tool creates a real ambiguity the description does not resolve.

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