Skip to main content
Glama
deyikong

SendGrid MCP Server

by deyikong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Email Statistics by Browser

get_stats_by_browser
Read-onlyIdempotent

Retrieve email click and unique click statistics grouped by browser type. Use this to compare browser performance and target follow-ups accordingly.

Instructions

Retrieve email statistics grouped by browser type. Only clicks and unique_clicks metrics are available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to return per page (SendGrid defaults to 500)
offsetNoNumber of results to skip for pagination
browsersNoComma-separated list of browsers to filter by
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

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
Behavior4/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 no safety contradiction exists. The description adds meaningful behavioral context beyond annotations by explicitly stating that only clicks and unique_clicks metrics are available, which prevents the agent from expecting open or send metrics.

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 two short sentences with no redundant filler. The primary action and grouping are front-loaded, and the critical metric limitation is stated immediately after.

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 tool, the description plus fully documented schema cover the essential information: what is returned, how to filter, how to paginate, and how to aggregate. It is slightly incomplete in not situating the tool among its sibling stats tools, but this is a minor gap given the schema richness and annotations.

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 the schema fully documents all six parameters, including defaults, formats, and pagination semantics. The description does not add parameter-specific meaning, but it also does not need to because the schema already carries the burden.

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 states a specific verb ('Retrieve'), a clear resource ('email statistics'), and the grouping dimension ('browser type'). This distinguishes it from sibling stats tools like get_stats_by_client_type and get_stats_by_country, and it also narrows the available metrics to clicks and unique_clicks.

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 description clearly implies use when browser-level click statistics are needed, but it provides no explicit guidance about when to prefer this tool over the many sibling stats tools. It does not mention alternatives or exclusion criteria such as 'for device-level stats, use get_stats_by_device_type'.

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