Skip to main content
Glama
deyikong

SendGrid MCP Server

by deyikong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Email Statistics by Mailbox Provider

get_stats_by_mailbox_provider
Read-onlyIdempotent

Retrieve email statistics grouped by mailbox provider to compare delivery and engagement metrics like bounces, clicks, and opens across Gmail, Outlook, Yahoo, and others.

Instructions

Retrieve email statistics grouped by mailbox provider (Gmail, Outlook, Yahoo, etc.). Broadest metric set of all stats breakdowns: blocks, bounces, clicks, deferred, delivered, drops, opens, processed, requests, spam_reports, unique_clicks, unique_opens. Note: no unsubscribes metric.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to return per page (SendGrid defaults to 500)
offsetNoNumber of results to skip for pagination
end_dateNoEnd date in YYYY-MM-DD format (defaults to today)
start_dateYesStart date in YYYY-MM-DD format
aggregated_byNoHow to group the statisticsday
mailbox_providersNoComma-separated list of mailbox providers to filter by

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Number of results to return per page (SendGrid defaults to 500)",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Number of results to skip for pagination",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}
  2. Changed2 schema fields changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context by enumerating the returned metrics and noting the absence of unsubscribes, but does not discuss pagination or response structure beyond what the schema implies.

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 sentences with no filler: the first states the core function, the second lists the full metric scope, and the third flags a meaningful omission. Every sentence earns its place and the key purpose is front-loaded.

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 read-only stats retrieval with fully documented parameters and clear annotations, the description covers what an agent needs to select and invoke the tool. The lack of an output schema is mitigated by the explicit metric list, though slightly more guidance on when this tool is preferred over sibling stats tools would make it complete.

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 parameters are already fully documented. The description adds context about the grouping and metric set but does not explain any parameter semantics beyond what the input schema provides, matching the baseline.

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 uses a specific verb ('Retrieve') and a clear resource ('email statistics grouped by mailbox provider') with concrete examples. It also differentiates itself from sibling stats tools by being the 'Broadest metric set of all stats breakdowns' and explicitly listing supported metrics.

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?

The description makes the grouping dimension explicit and signals when this tool is appropriate through 'Broadest metric set of all stats breakdowns.' It does not explicitly name alternatives or state when not to use it, so it stops short of full exclusion guidance.

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

Deploy Server

Other Tools