Skip to main content
Glama
Garoth

SendGrid MCP Server

by Garoth

get_stats

Retrieve SendGrid email analytics for specified date ranges to monitor campaign performance and engagement metrics.

Instructions

Get SendGrid email statistics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_dateYesStart date in YYYY-MM-DD format
end_dateNoEnd date in YYYY-MM-DD format (optional)
aggregated_byNoHow to aggregate the statistics (optional)

Implementation Reference

  • The core handler function within SendGridService that fetches email statistics from the SendGrid API using the /v3/stats endpoint.
    async getStats(params: {
      start_date: string;
      end_date?: string;
      aggregated_by?: 'day' | 'week' | 'month';
    }): Promise<SendGridStats> {
      const [response] = await this.client.request({
        method: 'GET',
        url: '/v3/stats',
        qs: params
      });
      return response.body as SendGridStats;
    }
  • Tool definition registration including name, description, and input schema validation.
    {
      name: 'get_stats',
      description: 'Get SendGrid email statistics',
      inputSchema: {
        type: 'object',
        properties: {
          start_date: {
            type: 'string',
            description: 'Start date in YYYY-MM-DD format'
          },
          end_date: {
            type: 'string',
            description: 'End date in YYYY-MM-DD format (optional)'
          },
          aggregated_by: {
            type: 'string',
            enum: ['day', 'week', 'month'],
            description: 'How to aggregate the statistics (optional)'
          }
        },
        required: ['start_date']
      }
    },
  • MCP tool call dispatcher that invokes the service handler and serializes the stats response as JSON text.
    case 'get_stats':
      const stats = await service.getStats(args);
      return { content: [{ type: 'text', text: JSON.stringify(stats, null, 2) }] };
  • TypeScript interface for the output type SendGridStats, defining the structure of the API response.
    export interface SendGridStats extends Array<{
      date: string;
      stats: Array<{
        metrics: {
          opens: number;
          clicks: number;
          bounces: number;
          spam_reports: number;
          unique_opens: number;
          unique_clicks: number;
          blocks: number;
          delivered: number;
          bounce_drops?: number;
          deferred?: number;
          invalid_emails?: number;
          processed?: number;
          requests?: number;
          spam_report_drops?: number;
          unsubscribe_drops?: number;
          unsubscribes?: number;
        };
      }>;
    }> {}
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get' implies a read operation, but the description doesn't mention authentication requirements, rate limits, data freshness, or what specific statistics are returned (e.g., opens, clicks, bounces). For a statistics tool with zero annotation coverage, this is inadequate.

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 a single, efficient sentence with zero wasted words. It's appropriately sized for a simple retrieval tool and gets straight to the point without unnecessary elaboration.

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?

For a statistics retrieval tool with no annotations and no output schema, the description is insufficient. It doesn't explain what kind of statistics are returned, their format, or any behavioral constraints. Given the complexity of email analytics and the lack of structured output documentation, more context is needed.

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%, with all parameters clearly documented in the schema. The description adds no additional parameter information beyond what's already in the structured data, so it meets the baseline expectation but doesn't provide extra value.

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 'Get SendGrid email statistics' clearly states the verb ('Get') and resource ('SendGrid email statistics'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_single_send' or 'get_template' that also retrieve data, so it misses full sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'get_single_send' and 'get_template' that retrieve specific email-related data, there's no indication of when statistical data is preferred over individual records or other email metrics.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Garoth/sendgrid-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server