Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get an event's custom properties

analytics_getEventDataById
Read-onlyIdempotent

Returns the custom property records, data types, and values attached to a specific event.

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>",
      "eventId": "<eventId>"
    },
    "name": "analytics_getEventDataById"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesThe Sextant site ID.
eventIdYesID of the event.
objectIdNoOptional: a short link or tracking pixel of this site, to read its analytics instead of the site's.

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?

The annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds the useful fact that the payload includes data types alongside values, but says nothing about result size, ordering, or what happens when an event has no custom properties.

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 front-loaded sentence with no filler; the resource scope and returned fields are stated immediately. It is arguably too terse rather than padded, which is a completeness issue rather than a conciseness one.

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 carries the burden of describing the return value, and it only names the categories (records, data types, values) without the shape of the records. For a simple two-required-parameter read tool this is minimally adequate, but an agent cannot predict the response structure.

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 all three parameters are documented in the schema, including objectId's override behavior. The description adds no parameter-level meaning beyond that, so the baseline of 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?

States a specific verb ('Returns') and a precisely scoped resource: the custom property records, data types, and values for a single event. An agent can tell this is a per-event property lookup rather than a series/stats tool, though it never explicitly contrasts itself with the near-identical sibling analytics_getEventDataProperties.

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?

No when-to-use guidance at all: nothing says to call this instead of analytics_getEventDataProperties or analytics_getEventDataValues, nor mentions prerequisites such as needing a siteId scoped to the event's site. The agent must infer intent from the name alone.

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