Scribe Mail

Visitor acquisition breakdown (first-touch)

get_visitor_breakdown

Read-onlyIdempotent

Rank which signature template or teammate acquired the most identified visitors (the first signature click that drove their first visit): { data:[{id, label, count}], pagination }.

Input Schema

Name	Required	Description
`page`	No	1-based page (default 1).
`limit`	No	Page size 1–100 (default 20).
`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."
`group_by`	Yes	Rank acquisition by the first-touch dimension: signature_template \| teammate.

Output Schema

Name	Required	Description	Default
`data`	Yes
`pagination`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 28, 2026
- removedOutput schema / properties / data / items / properties / label / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / label / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedOct 16, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds the attribution semantics and sketches the return payload, but says nothing about the aggregation time window, which is the main behavioral unknown an agent would have for an analytics call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that leads with the ranking verb and the acquisition metric. The trailing {data:[...], pagination} sketch is mildly redundant given an output schema exists, but it is compact and not a distraction.

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?

With a full output schema and fully described parameters, the description only needs to supply the metric definition, which it does. The one meaningful omission is the time period the breakdown covers – an agent cannot tell whether it is all-time or a default window.

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 coverage is 100% and page/limit/context/group_by are all documented in the schema, so parameter semantics are largely handled there. The description only restates the group_by dimension ('signature template or teammate') without adding format or default detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb (rank) and resource (identified visitors acquired by signature template or teammate) and defines the attribution rule behind it. An agent can distinguish it from list_visitors or get_analytics_views, though it never explicitly points at those siblings.

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?

The definition of first-touch ('first signature click that drove their first visit') implies the intended question – which template or teammate drives acquisition – but there is no explicit when-to-use, exclusion, or named alternative among get_analytics_clicks, get_analytics_views, or list_visitors.

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.