Skip to main content
Glama
sudomichael

Gizmo Analytics

by sudomichael
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

get_breakdown

Read-onlyIdempotent

Retrieve top-N breakdowns for built-in analytics dimensions like page, country, browser, or device. Apply optional filters and custom date ranges to focus on specific segments.

Instructions

Top-N for any column-backed dimension: page, referrer, country, region, city, browser, device, language, screen, channel, ai_source, hostname. Use this for "top countries / browsers / devices / channels / AI sources / cities / etc." — anything in the dashboard's breakdown tabs. For custom event properties (UTM rollups, plan splits, anything you ship in event JSON), use breakdown_by_property instead. Filters and custom date ranges supported.

Optional dimension filters. Each filter is {dim, op, value}. Available dims: page, entry_page, exit_page, referrer, hostname, channel, ai_source, utm_source, utm_medium, utm_campaign, country, region, city, language, device, browser, screen, event_name, or prop:. Available ops: is, is_not, contains, not_contains. Filters AND together. Example: [{dim:'country', op:'is', value:'US'}, {dim:'device', op:'is_not', value:'mobile'}].

Optional date range. Either {preset:'last_7_days'} (also: today, yesterday, last_14_days, last_30_days, last_90_days, last_year, month_to_date, last_month, all_time) OR {from:'2026-05-01', to:'2026-05-15'} for a custom range (ISO 8601 dates or timestamps). Defaults vary by tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dimensionYesWhich built-in dimension to group by: page, referrer, country, region, city, browser, device, language, screen, channel, ai_source, or hostname.
site_idNoInternal site UUID. Get one from list_sites. Omit to scope to the entire workspace.
date_rangeNoOptional date range. Either {preset:'last_7_days'} OR {from:'2026-05-01', to:'2026-05-15'}. Defaults per tool — usually last_7_days.
filtersNoAND-joined dimension filters.
limitNoMax number of rows to return. Defaults to 20, capped at 200. Pagination via date_range for larger windows.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rowsYesTop-N rows sorted by visitor count, descending.

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds that filters are AND-joined and date ranges have defaults, but does not contradict annotations. No behavioral surprises.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two paragraphs: first sets purpose and use case, second details parameters with clear examples. No redundancy, every sentence contributes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all 5 parameters, output schema exists, differentiates from sibling, explains constraints (max limit, date range defaults). Complete for a query tool with solid annotations.

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 100%, but description adds meaning beyond field types: explains filter logic (AND), provides examples, notes default behaviors for date_range, and clarifies limit's max and pagination. Adds moderate value.

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?

Clearly states the tool provides 'Top-N for any column-backed dimension' and lists the dimensions. Differentiates from sibling `breakdown_by_property` by specifying use for built-in dimensions vs custom event properties.

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

Usage Guidelines5/5

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

Explicitly tells when to use this tool: for dashboard breakdown tabs on built-in dimensions. Directs to `breakdown_by_property` for custom properties. Includes filter and date range usage details.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sudomichael/gizmoanalytics-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server