Tracklution

Query raw events (legacy)

query_events

Read-only

Legacy tool: lists events from the v2 store, which keeps only about the last 7-14 days. search_events lists the same events from data_from on (about the last 6 months), with more filters. Paged with meta.cursor.next_cursor.

Input Schema

Name	Required	Description
`cursor`	No	Pagination cursor from a previous response's meta.cursor.next_cursor.
`source`	No	Filter by traffic source
`status`	No	Filter by event status. Default: "processed" (real, successfully-recorded events — what nearly every analytics question is about). Override only for debugging: "pending" (queued), "error" (processing failed), "rejected" (validation/spam blocked).
`date_to`	Yes	End date (YYYY-MM-DD)
`has_epik`	No	Only events arriving with a Pinterest epik
`per_page`	No	Items per page (default 50, max 1000 on v2). v2 SQLite reads are fast enough to prefer larger pages over more cursor round-trips.
`date_from`	Yes	Start date (YYYY-MM-DD)
`has_adfcd`	No	Only events arriving with an Adform adfcd
`has_gclid`	No	Only events arriving with a Google Ads gclid
`event_name`	No	Filter by event name
`has_fbclid`	No	Only events arriving with a Facebook fbclid
`has_lsclid`	No	Only events arriving with an lsclid
`has_scclid`	No	Only events arriving with a Snapchat scclid
`has_ttclid`	No	Only events arriving with a TikTok ttclid
`has_ga4clid`	No	Only events arriving with a GA4 client ID
`has_msclkid`	No	Only events arriving with a Microsoft msclkid
`has_rdt_cid`	No	Only events arriving with a Reddit rdt_cid
`server_name`	No	Server name (required when connected to multiple servers).
`container_id`	Yes	Container ID (starts with "trc_").
`has_li_fat_id`	No	Only events arriving with a LinkedIn li_fat_id

Output Schema

Name	Required	Description	Default
`meta`	Yes
`events`	Yes
`warnings`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 20, 2026
- changedOutput schema / properties / events / items / additionalProperties
```
Previous value: -falseNew value: +true
```
- addedOutput schema / properties / events / items / properties / has_ndclid
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / events / items / properties / has_ob_click_id
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / events / items / properties / has_propeller_click_id
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / events / items / properties / has_twclid
```
Added value: +{
+  "type": "boolean"
+}
```
- changedOutput schema / properties / meta / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedOutput schema / properties / meta / properties / cursor / additionalProperties
```
Previous value: -falseNew value: +true
```
First observedSep 18, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the 7-14 day retention window and the pagination contract (meta.cursor.next_cursor), which are the two things an agent would otherwise get wrong. It does not discuss cost/rate limits, but for a read tool with an output schema that is minor.

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?

Three short sentences, zero filler, with the legacy status and retention limit front-loaded before the sibling comparison. Every sentence carries information the agent needs.

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?

For a 20-parameter legacy tool this is complete on the dimensions that matter — scope, retention, deprecation status, and pagination — and an output schema exists so return values need not be explained. Only the absence of explicit cost/performance guidance keeps it from a 5.

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% across all 20 parameters, so filtering semantics (status default, per_page guidance, clid flags) are already fully documented. The description only restates the cursor mechanism, adding nothing beyond the schema — baseline 3 is appropriate.

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 verb+resource ("lists events from the v2 store") and immediately contrasts it with the sibling search_events, including what each covers. An agent can tell it apart from list_events/search_events without opening a schema.

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

Usage Guidelines4/5

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

Names the alternative (search_events) and its advantages — 6-month window and more filters — which implicitly routes the agent away from this tool for anything beyond ~2 weeks. It stops short of an explicit "use this only when..." rule, but the decision context is clear.

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

All Tracklution tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?