Scribe Mail

List analytics events

list_analytics_events

Read-onlyIdempotent

List the raw conversion events recorded for the workspace (from the website SDK and server-to-server calls), most recent first, one row per event with its attribution uuids and its properties returned as recorded. Use it to verify that conversion tracking works, to read one visitor's event history (distinct_id) or to export rows. For counts, revenue or rankings use get_analytics_events_summary instead, which aggregates; for signature views and clicks use get_analytics_views / get_analytics_clicks; for visitor profiles use list_visitors. Events are ingested asynchronously, so one tracked seconds ago may not show yet. Read-only; needs the analytics:read scope and a plan with event tracking (403 otherwise). Returns one page (default 50, max 100); set auto_paginate to fetch up to max_pages, and truncated: true means more remain.

Input Schema

Name	Required	Description
`name`	No	Filter to one event name (exact match).
`page`	No	1-based page (default 1).
`limit`	No	Page size, 1–100 (default 50).
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`country`	No	Filter to one country (ISO 3166-1 alpha-2, case-insensitive, e.g. FR).
`end_date`	No	Range end (inclusive), ISO-8601 date YYYY-MM-DD.
`max_pages`	No	Page cap when auto_paginate is true (default 5).
`start_date`	No	Range start (inclusive), ISO-8601 date YYYY-MM-DD. Omit both dates for all time.
`distinct_id`	No	Filter to one identified visitor's event history: their user id, the `distinct_id` from list_visitors (exact match).
`teammate_id`	No	Filter to one teammate (UUID from list_teammates); unknown returns 404.
`auto_paginate`	No	Fetch multiple pages up to `max_pages` (default false).
`marketing_campaign_id`	No	Filter to one marketing campaign (UUID from list_marketing_campaigns); unknown returns 404.
`signature_template_id`	No	Filter to one signature template (UUID from list_signatures); unknown returns 404.

Output Schema

Name	Required	Description
`data`	Yes
`truncated`	Yes	True when auto_paginate stopped at max_pages with more results remaining.
`pagination`	Yes
`pages_fetched`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed24 schema fields changedOct 28, 2026
- removedOutput schema / properties / data / items / properties / anchor_uuid / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / anchor_uuid / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / anonymous_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / anonymous_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / click_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / click_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / country_code / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / country_code / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / currency / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / currency / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / distinct_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / distinct_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / email_uuid / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / email_uuid / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / marketing_campaign_uuid / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / marketing_campaign_uuid / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / recorded_at / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / recorded_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / signature_template_uuid / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / signature_template_uuid / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / source / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / source / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / teammate_uuid / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / teammate_uuid / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed6 schema fields changedOct 16, 2026

changedInput schema / properties / country / description

Previous value: -"Filter to one country (ISO 3166-1 alpha-2)."New value: +"Filter to one country (ISO 3166-1 alpha-2, case-insensitive, e.g. FR)."

changedInput schema / properties / distinct_id / description

Previous value: -"Filter to one identified visitor (their user id) — their event history."New value: +"Filter to one identified visitor's event history: their user id, the `distinct_id` from list_visitors (exact match)."

changedInput schema / properties / marketing_campaign_id / description

Previous value: -"Filter to one marketing campaign (UUID)."New value: +"Filter to one marketing campaign (UUID from list_marketing_campaigns); unknown returns 404."

changedInput schema / properties / signature_template_id / description

Previous value: -"Filter to one signature template (UUID)."New value: +"Filter to one signature template (UUID from list_signatures); unknown returns 404."

changedInput schema / properties / start_date / description

Previous value: -"Range start (inclusive), ISO-8601 date YYYY-MM-DD."New value: +"Range start (inclusive), ISO-8601 date YYYY-MM-DD. Omit both dates for all time."

changedInput schema / properties / teammate_id / description

Previous value: -"Filter to one teammate (UUID)."New value: +"Filter to one teammate (UUID from list_teammates); unknown returns 404."

First observedOct 16, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnly/destructive/idempotent, but the description adds material context beyond them: async ingestion means recent events may be missing, it requires the analytics:read scope and an event-tracking plan (403 otherwise), and it documents pagination behavior including auto_paginate/max_pages and the `truncated: true` overflow signal.

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?

Dense but front-loaded: purpose and return shape first, then use cases, then sibling routing, then caveats (async, auth/plan, pagination). Every sentence carries distinct information; nothing is redundant padding despite the length.

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 everything an agent needs: what is returned, ordering, ingestion lag, permission/plan failure mode, and pagination semantics including the truncation signal. With an output schema present, return-value details need not be repeated, and the description still tells the agent enough to call and interpret results correctly.

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 the schema already documents every parameter and baseline is 3. The description adds value by explaining the interaction of the pagination params (one page default 50/max 100; auto_paginate fetches up to max_pages) and by framing distinct_id in terms of the list_visitors workflow, which is more than the schema states.

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?

Starts with a specific verb and resource ('List the raw conversion events recorded for the workspace') and immediately states scope and ordering ('most recent first, one row per event'). It also names the data sources (website SDK, server-to-server) which disambiguates it from the summary/view/click siblings.

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?

Gives three concrete use cases (verify tracking, read one visitor's history via distinct_id, export rows) and then explicitly routes alternative needs: get_analytics_events_summary for counts/revenue/rankings, get_analytics_views/clicks for signature views and clicks, list_visitors for profiles. Explicit when-to-use and when-to-use-something-else.

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

All Scribe Mail 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.