Skip to main content
Glama

ADS Beast

audit_tracking

Read-only

Tracking diagnostics for a client: pixel, GA4 and GTM mismatches on the landing page, conversion actions and the other tracking guards in one report.

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": {
      "client_id": "<client_id>"
    },
    "name": "audit_tracking"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds real scope information — which tracking layers are inspected (pixel, GA4, GTM) and that results are consolidated into a single report — but says nothing about whether it fetches the live page, how long it takes, or what happens when a layer is absent.

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?

One front-loaded sentence with no filler; the resource is stated first and the check list follows. Slightly dense phrasing ('the other tracking guards') costs a little precision but nothing is wasted.

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 single-parameter, read-only diagnostic with no output schema, the definition covers what is inspected and that output is one report, which is the essential shape. It stops short of describing report contents or the client_id lookup expectation, leaving a modest gap.

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 0% for the single parameter client_id. The phrase 'for a client' implicitly maps to client_id and confirms it scopes the audit to one client, which is the main semantic the agent needs, but no format, source, or lookup guidance is given.

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 resource ('tracking diagnostics for a client') and enumerates the concrete checks performed: pixel, GA4 and GTM mismatches on the landing page, conversion actions, and 'other tracking guards.' This is far more specific than a tautology and lets an agent distinguish it from broader siblings like audit_account or seo_technical_audit, though it never explicitly contrasts itself with google_ads_conversion_tracking_check.

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 when-to-use statement, no exclusions, and no named alternative. The agent must infer from the wording that this is the consolidated landing-page tracking audit rather than a per-platform check. 'In one report' hints at consolidation but does not function as routing guidance.

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.