Skip to main content
Glama
sudomichael

Gizmo Analytics

by sudomichael
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

query_events

Read-onlyIdempotent

Query raw analytics events with filters on dimensions like page, country, device, and custom properties. Supports date ranges and pagination up to 1,000 events per call.

Instructions

Query raw events. Default returns the latest 100; max 1000 per call. For large analyses, paginate by date_range. Filters 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
site_idNoInternal site UUID. Get one from list_sites. Omit to scope to the entire workspace.
event_nameNoCustom event name (1–64 chars, alphanumeric + dot/dash/underscore). Optional when querying all events.
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 events to return. Defaults to 100, capped at 1000.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventsYesRaw event rows, newest first. Up to opts.limit (default 100, max 1000).

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds behavioral context: default limit, max cap, filtering mechanics, date range options, and implicit pagination. No contradictions.

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?

Description is structured into clear paragraphs: summary, limits, filters, date range. Every sentence adds value with no redundancy. Front-loaded with key info.

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?

Given 5 parameters, full schema descriptions, output schema presence, and rich annotations, the description covers all necessary aspects: default behavior, filtering, date ranges, limits. No gaps for the agent to infer.

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%, so baseline is 3. The description adds significant value beyond schema: lists all available dims and ops, provides filter example, explains preset and custom date ranges. This enriches semantic understanding.

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?

The description states 'Query raw events' explicitly, defines default behavior (latest 100, max 1000), and provides pagination advice. The verb+resource is clear and distinguishes from analytic siblings like breakdown_by_property or get_site_traffic.

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?

Description advises pagination for large analyses and notes that defaults vary by tool, but does not explicitly state when to avoid this tool or name alternatives. Some usage context is given, but no exclusions or sibling comparisons.

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