Skip to main content
Glama

Detect analytics, ad and tracking scripts on a web page (Google Analytics/Tag Ma

trackers
Read-only

Detect analytics, ad and tracking scripts on a web page (Google Analytics/Tag Manager, Meta Pixel, TikTok, LinkedIn, Hotjar, Clarity, Segment, Mixpanel, HubSpot, Plausible...), cookie-consent tools and all third-party script domains. Fast (1-3 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.003 per call (x402, USDC on Base).

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>"
    },
    "name": "trackers"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered, and the description adds real behavioral context beyond them: expected latency of 1-3 s and a concrete quota/price model (20 free calls/day per user across free tools, then $0.003 per call via x402 USDC on Base). That is meaningful operational information for planning and for anticipating an unpaid-call response. It stops short of describing what the result contains (e.g. per-vendor detection status vs. a raw domain list).

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?

Front-loaded with the capability and vendor list, then latency, then cost - a sensible order with no filler sentences. The pricing clause is the longest part and is slightly dense (free tiers, per-call rate, x402/Base mechanics) but each element is actionable rather than padding.

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?

The tool is simple (one required URL, one optional payment token, no output schema), and the description supplies scope, speed and cost, which is most of what an agent needs to call it. The one remaining gap is the shape of the result - whether it returns per-vendor hits, a boolean, or a domain inventory - which matters for deciding whether to call this or a sibling.

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 are self-documented, including the non-obvious payment flow ('omit on the first call to get the price and requirements'), so the schema does the heavy lifting. The description's pricing sentence reinforces why a payment parameter exists, but adds no detail about the url parameter's constraints beyond the schema. Baseline 3 applies.

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 plus specific resource: 'Detect analytics, ad and tracking scripts on a web page', then enumerated vendor examples (Google Analytics/Tag Manager, Meta Pixel, TikTok, Hotjar, Segment...) and the additional scope of cookie-consent tools and third-party script domains. That scope makes it unmistakable against siblings like page_weight, headers or links, which cover adjacent but distinct page properties.

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 implied by the scope statement rather than stated: an agent can infer 'use this when you need to know what tracking tags a page loads', but there is no explicit when-to-use, when-not-to-use, or named alternative. No prerequisite is mentioned either, such as the URL needing to be publicly reachable (that only appears in the schema).

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.