Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

List my tracking pixels

analytics_getPixels
Read-onlyIdempotent

Returns a paginated list of the current user's tracking pixels, with search and sorting options.

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": "analytics_getPixels"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
searchNoSearch text used to filter results.
siteIdYesThe Sextant site ID.
orderByNoField to sort the results by.
pageSizeNoNumber of results per page.
maxResultsNoMaximum number of results to include.
sortDescendingNoWhether to sort results in descending order.

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. The description adds only that results are paginated and support search/sort, which is modest context beyond the structured fields; it says nothing about default ordering, result caps, or empty-result behavior.

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 well-formed sentence with the resource front-loaded and no filler. It is arguably too terse for a 7-parameter tool, but nothing in it 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?

With no output schema, the description must carry the return-shape burden, and 'paginated list' plus 'search and sorting options' only partially does so. For a 7-parameter read tool the essentials are covered by annotations and schema, but the description leaves the caller to infer pagination semantics and the shape of returned pixel records.

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%, so every parameter including page, pageSize, maxResults, orderBy, sortDescending, search, and siteId is already documented in the schema. The description only restates that search and sorting exist, adding no format details, defaults, or interaction rules (e.g., how maxResults relates to pageSize). 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 gives a specific verb and resource ('Returns a paginated list of the current user's tracking pixels') and scopes it to the current user. It is clearly distinct from the singular analytics_getPixel sibling by virtue of 'list', though it never explicitly names that alternative.

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?

It states what the tool returns but gives no guidance on when to use it versus analytics_getPixel or the tracking_* siblings, and no prerequisites or exclusions. The 'search and sorting options' mention hints at filtering use cases but does not route the agent between alternatives.

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