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

TableJSON 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

TableJSON 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.

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.7/5.0

Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, and the description confirms 'Read-only' consistently while adding information the annotations cannot carry: asynchronous ingestion lag, the required analytics:read scope plus plan gating with a 403 outcome, and pagination semantics including the truncated flag. That is substantive context beyond the structured safety hints.

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?

Four sentences, each load-bearing: what is returned, when to use it and what to use instead, the freshness caveat, and the auth/pagination contract. Information is front-loaded with the resource and result shape before the caveats.

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?

For a 13-parameter, high-complexity list tool with an output schema and full annotation coverage, the description supplies everything else an agent needs: routing, async staleness, permission/plan failure mode, and page limits. Return-value detail is correctly left to the output schema.

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% and all 13 parameters are documented in the schema, so the baseline is 3. The description restates the pagination behavior (auto_paginate up to max_pages, truncated meaning more remain) and one filter usage (distinct_id for a visitor's history), but adds little that the schema fields do not already say.

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 opening sentence gives a specific verb+resource+scope: raw conversion events for the workspace, sourced from the website SDK and server-to-server calls, most recent first, one row per event. It also names the sibling alternatives (get_analytics_events_summary, get_analytics_views/clicks, list_visitors), so an agent can distinguish it without opening any schema.

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?

Explicit when-to-use cases are given (verify conversion tracking, read one visitor's history via distinct_id, export rows) and explicit when-not-to-use routing is provided for three sibling families. This is a complete routing guide, not an implied one.

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.