Skip to main content
Glama

Check third-party scripts and cookies on a page

trackers
Read-only

Third-party script and iframe hosts on a page, each classified (analytics, ads, tag manager, chat, session replay, social, consent, CDN), the cookies its first response sets (names and flags only, never values) and whether a known consent manager is present. Static HTML only: scripts added at run time are not seen. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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
urlYesPage address, https://…

Output Schema

NameRequiredDescriptionDefault
urlNo
noteNo
sourceNo
checkedAtNo
categoriesNo
cookiesSetNo
attributionNo
thirdPartiesNo
consentManagerNo
thirdPartyCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond readOnlyHint and openWorldHint, it discloses the pricing model ($0.002 per successful call), the payment rail (x402, USDC on Base, Solana and 10 more networks), and that failed calls are not charged — critical for an agent deciding whether to invoke. It also states a privacy-relevant behavior the annotations cannot convey: cookies are returned as names and flags only, never values, and results are scoped to static HTML.

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?

Three sentences, each doing a distinct job: what is returned first, then the static-HTML limitation, then cost. No filler or repetition. The first sentence is a long list-stuffed run-on that takes effort to parse, which is the only structural weakness.

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

Completeness5/5

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

For a one-parameter, read-only, open-world tool with an output schema already documenting return shape, the description covers everything an invoking agent needs: result contents, classification scheme, privacy handling of cookie values, the static-HTML scope limit, and the exact cost and payment mechanism including failure billing.

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?

With a single required parameter at 100% schema description coverage ('Page address, https://…'), the schema already carries the full parameter meaning. The description adds only an implied constraint that one page is analyzed per call, not any format or parsing detail 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?

The description names the exact resource set: third-party script and iframe hosts, the cookies set on first response, and consent-manager presence, plus the concrete classification taxonomy (analytics, ads, tag manager, chat, session replay, social, consent, CDN). An agent knows precisely what comes back. It stops short of a verb-first phrasing and does not distinguish itself from any named sibling, which keeps it at 4 rather than 5.

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

Usage Guidelines4/5

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

It supplies a clear applicability boundary with 'Static HTML only: scripts added at run time are not seen,' which tells the agent when this tool will under-report and therefore when not to rely on it. It does not name an alternative tool for the runtime-rendered case or state prerequisites beyond that, so it falls short of a full when/when-not/alternatives treatment.

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