Skip to main content
Glama

sendgrid

by io.usefulapi

Get email stats

sendgrid_get_stats
Read-only

Get global email statistics over a date range (delivered, opens, clicks, bounces, spam reports, etc.). Returns an array of { date, stats: [{ metrics: {...} }] }. SendGrid: GET /v3/stats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to return.
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 (required).
aggregated_byNoHow to group the returned statistics.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The description reveals the API endpoint (GET /v3/stats) and the exact return structure ('array of { date, stats: [{ metrics: {...} }] }'), adding context beyond the readOnlyHint annotation. It doesn't discuss rate limits or pagination behavior, but the schema covers pagination parameters.

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?

The description is three sentences, front-loaded with the main verb and resource, and includes both return format and API endpoint in a minimally verbose way. Every sentence adds value without redundancy.

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 lacking an output schema, the description clearly states the return format, and the schema fully documents parameters. With readOnlyHint present and a simple read operation, the description covers all essential aspects for correct invocation.

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?

The input schema provides full descriptions for all 5 parameters (100% coverage), so the baseline is 3. The description's mention of 'date range' aligns with start_date/end_date but adds no new parameter-specific details beyond the schema.

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 clearly states the tool's function: 'Get global email statistics over a date range' and lists specific metrics (delivered, opens, clicks, bounces, spam reports). This distinguishes it from sibling tools focused on contacts, templates, bounces, and sending.

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 provides clear context that this tool retrieves global email statistics, which implies when to use it for overall metrics. It doesn't explicitly mention exclusions or alternatives, but the distinct domain of each sibling tool makes the usage clear enough.

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

All sendgrid toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct resource/action: send mail, manage contacts (upsert/count/search), templates (get/list), suppression lists (bounces/unsubscribes), marketing lists, stats, and health check. No overlaps or ambiguous boundaries.

Naming Consistency5/5

All tools follow a consistent 'sendgrid_' prefix with a verb_noun pattern (e.g., get_template, list_bounces, send_mail). The only minor deviation is 'ping' for health check, but it's a conventional verb-only name and doesn't break the overall consistency.

Tool Count5/5

11 tools is well-scoped for a SendGrid server, covering sending, contacts, templates, suppression, stats, and health. Each tool has a clear purpose and none feel redundant.

Completeness4/5

Core email sending, contact management, and read operations for templates/suppression are covered. However, there are no write operations for templates (create/update/delete) or suppression list management (remove), which are minor gaps that agents can work around by using the existing tools.

Resources