Tracklution

Query raw sessions (legacy)

query_sessions

Read-only

Legacy tool: lists sessions from the v2 store, which keeps only about the last 7-14 days. search_sessions lists the same sessions from data_from on (about the last 6 months), with report-dimension 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
`date_to`	Yes	End date (YYYY-MM-DD)
`has_epik`	No	Only sessions 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 sessions arriving with an Adform adfcd
`has_gclid`	No	Only sessions arriving with a Google Ads gclid
`has_fbclid`	No	Only sessions arriving with a Facebook fbclid
`has_lsclid`	No	Only sessions arriving with an lsclid
`has_scclid`	No	Only sessions arriving with a Snapchat scclid
`has_ttclid`	No	Only sessions arriving with a TikTok ttclid
`has_ga4clid`	No	Only sessions arriving with a GA4 client ID
`has_msclkid`	No	Only sessions arriving with a Microsoft msclkid
`has_rdt_cid`	No	Only sessions 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 sessions arriving with a LinkedIn li_fat_id

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is clear. The description adds valuable context beyond annotations: the v2 store retention window of roughly 7-14 days and the pagination mechanism via meta.cursor.next_cursor.

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 with no wasted text. It is front-loaded with the legacy status and immediately gives the sibling comparison and pagination behavior.

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?

Despite 18 parameters, the schema fully documents them and an output schema exists. The description supplies the critical missing context: legacy retention limits, the search_sessions alternative, and cursor pagination.

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 18 parameters are already documented in the input schema. The description adds only high-level pagination context and the legacy date-range limitation; it does not need to explain individual filter parameters.

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 a specific verb and resource: lists sessions from the legacy v2 store. It explicitly distinguishes this from the sibling search_sessions, which covers a longer period and supports report-dimension filters.

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?

It names the alternative search_sessions and explains the key selection condition: search_sessions covers roughly six months with filters, while this legacy tool is limited to about 7-14 days. An agent can route correctly without opening either schema.

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?