Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get a tracking pixel

analytics_getPixel
Read-onlyIdempotent

Returns the specified tracking pixel and its configuration.

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

Input Schema

NameRequiredDescriptionDefault
siteIdYesThe Sextant site ID.
pixelIdYesID of the tracking pixel.

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, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description's help. The description adds only that the response includes the pixel 'and its configuration', which is a small but genuine hint about payload content; it says nothing about error behavior for unknown pixelId or site scoping.

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?

A single short sentence with no filler or redundancy. It is appropriately sized for a simple read tool, though it front-loads very little beyond restating the name and title.

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 two-parameter read tool with rich annotations, the definition is functional but thin: with no output schema, the description is the only place to explain what a 'pixel configuration' payload contains, and it does not. Adequate to invoke, but leaves the agent guessing about the response shape.

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 100%, with both siteId and pixelId documented in the schema itself, so the description carries no additional parameter burden. It adds no format, prefix, or cross-parameter constraints beyond what the schema already states, which is the expected baseline.

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 verb ('Returns') and resource ('tracking pixel') and the word 'specified' signals a single-resource lookup rather than a listing. It does not explicitly distinguish itself from the sibling analytics_getPixels (list) or tracking_get_code, so it stops short of full sibling differentiation.

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 guidance, no mention of prerequisites or permissions, and no reference to an alternative such as analytics_getPixels for enumeration. The agent must infer usage entirely from the tool name and the required IDs.

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