Skip to main content
Glama

Tagely Analytics

Top values by dimension

get_breakdown
Read-onlyIdempotent

Top values of one dimension for a date range, for visitors and for conversions - the same breakdowns as the Tagely analytics page. url: page views (excluding bots) grouped by URL without query string; conversions not available for url. utm / referer / country / device: visitor counts are new visitors' entry views; conversion counts are conversion events, attributed by the event's own UTMs (utm) or by the converting visitor's entry view (referer, country, device). Bots excluded. Device codes: D desktop, M mobile, T tablet.

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": {
      "dimension": "<dimension>"
    },
    "name": "get_breakdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of top values, default 10 (20 for url).
periodNoDate range. last_7_days / last_30_days end yesterday (today excluded), as on the Tagely analytics page. Default last_7_days, or custom if start_date is given.
end_dateNoYYYY-MM-DD, for period=custom (inclusive). A custom range covers at most 366 days.
dimensionYes
start_dateNoYYYY-MM-DD, for period=custom (inclusive).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent, closed-world read, so the description is free to spend its words on semantics — and it does: bot exclusion, url stripping of query strings, visitor counts being new visitors' entry views, and conversion attribution differing by dimension (event UTMs vs. converting visitor's entry view). These are exactly the data-interpretation facts an agent cannot get from structured fields.

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?

Front-loaded with the core operation, then a dimension-by-dimension block that each earns its clause. The dense semicolon chaining makes it slightly hard to scan, but no sentence is filler and trimming would lose real semantics.

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?

With no output schema, the description carries responsibility for return values; it names the metric families and the notion of 'top values' but never states the record shape (value + count pairs) or ordering. For a filtered aggregation tool that is a modest gap, not a blocking one, since dimension semantics are fully spelled out.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80% and the schema already documents limit, period, and the date fields, so the baseline is 3. The description lifts this above baseline by giving meaning the enum lacks: the per-dimension metric definition and the D/M/T device code legend, plus the url-conversions unavailability that constrains valid dimension choices.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific operation (top values of one dimension over a date range) plus the two metric families returned (visitors and conversions), and then defines each of the five dimensions individually. An agent can tell this apart from get_summary or get_visitor_journey without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the description explains what each dimension yields and flags that conversions are unavailable for url, which implicitly guides dimension choice. It never says when to pick this over get_summary or get_visitor_journey, nor when a breakdown is the wrong call. Minimum-viable 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.

Resources