Skip to main content
Glama
Sign In
SendGrid MCP Server

SendGrid MCP Server

by deyikong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Statistics Overview

get_stats_overview
Read-onlyIdempotent

Retrieve email statistics for a chosen date range, grouped by day, week, or month, with optional subuser inclusion to identify performance trends and support data-driven decisions.

Instructions

Get a comprehensive overview of email statistics across multiple dimensions

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start_date": "<start_date>"
    },
    "name": "get_stats_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
include_subusersNoInclude subuser statistics in the overview

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
  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

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only a vague 'across multiple dimensions' scope and does not disclose any further behavioral traits such as aggregation behavior, time filtering, or response size; still, it does not contradict the annotations.

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?

The description is a single, front-loaded sentence with no filler or repetition. It is concise, though somewhat generic and under-specified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description does not explain what 'multiple dimensions' actually includes or what the returned overview looks like. Given the large set of sibling stats tools, this definition is too thin to let an agent confidently decide whether to call this tool or a more specific stats-by-dimension tool.

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%, so start_date, end_date, aggregated_by, and include_subusers are already documented in the input schema. The description adds no parameter-level meaning, which keeps this at the baseline rather than higher.

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?

The description identifies a clear verb ('get') and resource ('email statistics overview') and adds the qualifier 'across multiple dimensions,' which gives a reasonable sense of what the tool does. However, it does not name or contrast any sibling tools, so an agent cannot easily distinguish it from get_global_stats or get_stats_by_* variants.

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 phrase 'comprehensive overview ... across multiple dimensions' implies this tool is for broad, multi-dimensional email statistics rather than a single-dimension breakdown. But there is no explicit when-to-use/when-not-to-use guidance, no named alternatives, and no indication of how this tool differs from the many other stats tools in the sibling list.

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