Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get the tracking code

tracking_get_code
Read-onlyIdempotent

The code to paste before on every page of the site, built from its tracking options. The person installs it. Once it is installed, tracking_check with testVisit true visits the actual site and checks the installed code.

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": {
      "siteId": "<siteId>"
    },
    "name": "tracking_get_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real context beyond that: the output is derived from the site's configured tracking options, and a human must perform the install step, so the returned code is not self-installing. It does not describe the exact return shape (script tag vs. raw snippet), which is the only notable gap.

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 short sentences, front-loaded with what the tool produces and followed by the verification path. Slight redundancy between 'The person installs it' and 'Once it is installed', but no sentence is wasted.

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 single-parameter read tool with full annotation coverage and no output schema, the description covers purpose, configuration dependency, and the follow-up verification step. The main omission is what the return value actually looks like (snippet text vs. HTML script element), which matters for pasting into a page.

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 0% for the single siteId parameter, so the description must carry the burden. It references 'the site' and 'its tracking options', implying the input identifies which site's code is generated, but it never names the parameter or its format. Partial compensation only.

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 pins down exactly what is returned: an installable snippet to paste before </head> on every page of the site, built from the site's tracking options. It implicitly separates this from tracking_check (which verifies the installed code). It is phrased as a noun phrase rather than an explicit verb ('returns the code'), which keeps it just short of a 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 establishes the workflow clearly: this tool produces the code, a person installs it, and only after installation should tracking_check with testVisit true be used against the live site. That effectively tells the agent when to call this versus the sibling verification tool. There is no explicit 'do not use this when...' exclusion, so it falls short of a 5.

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