Skip to main content
Glama
deyikong

SendGrid MCP Server

by deyikong

Open Single Send Stats

open_single_send_stats

View detailed performance metrics for a specific SendGrid email campaign to analyze engagement and effectiveness.

Instructions

Open single send stats page for a specific campaign

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
singlesend_idYesThe single send ID to view stats for

Implementation Reference

  • The handler function for the 'open_single_send_stats' tool. It constructs a URL using the provided singlesend_id and returns a ToolResult with a text message instructing the user to open it in their browser.
    handler: async ({ singlesend_id }: { singlesend_id: string }): Promise<ToolResult> => {
      return {
        content: [
          {
            type: "text",
            text: `Please open this URL in your browser to view stats for single send ${singlesend_id}:\nhttps://mc.sendgrid.com/single-sends/${singlesend_id}/stats?view=raw`,
          },
        ],
      };
    },
  • Zod input schema defining the required 'singlesend_id' string parameter.
    inputSchema: {
      singlesend_id: z.string().describe("The single send ID to view stats for"),
    },
  • Local registration of the 'open_single_send_stats' tool within the campaignTools export.
    open_single_send_stats: {
      config: {
        title: "Open Single Send Stats",
        description: "Open single send stats page for a specific campaign",
        inputSchema: {
          singlesend_id: z.string().describe("The single send ID to view stats for"),
        },
      },
      handler: async ({ singlesend_id }: { singlesend_id: string }): Promise<ToolResult> => {
        return {
          content: [
            {
              type: "text",
              text: `Please open this URL in your browser to view stats for single send ${singlesend_id}:\nhttps://mc.sendgrid.com/single-sends/${singlesend_id}/stats?view=raw`,
            },
          ],
        };
      },
    },
  • Global registration by spreading campaignTools (which includes open_single_send_stats) into the allTools export used for MCP tools.
    export const allTools = {
      ...automationTools,
      ...campaignTools,
      ...contactTools,
      ...mailTools,
      ...miscTools,
      ...statsTools,
      ...templateTools,
    };
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'open stats page' which implies a UI or display action, but doesn't disclose behavioral traits such as whether this navigates to a web interface, requires specific permissions, or has rate limits. The description is minimal and lacks operational context.

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, direct sentence with no wasted words, clearly front-loading the purpose. It efficiently communicates the core action without redundancy or unnecessary detail, making it highly concise and well-structured.

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?

Given no annotations and no output schema, the description is incomplete for a tool that likely involves UI interaction or data retrieval. It fails to explain what 'open stats page' entails (e.g., returns a URL, displays data, or requires browser context), leaving significant gaps in understanding the tool's behavior and output.

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 the parameter 'singlesend_id' fully documented in the schema. The description adds no additional meaning beyond implying it's for a campaign, which aligns with the schema. Baseline score of 3 is appropriate as the schema handles parameter documentation effectively.

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 clearly states the action ('open stats page') and resource ('for a specific campaign'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_stats_overview' or 'get_category_stats' that also provide statistical information, missing explicit 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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'get_stats_overview' and 'get_category_stats' available, the description lacks any indication of context, prerequisites, or comparisons, leaving usage ambiguous.

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/deyikong/sendgrid-mcp'

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