Skip to main content
Glama
Garoth

SendGrid MCP Server

by Garoth

list_verified_senders

Retrieve all verified sender identities from your SendGrid account to manage email authentication and ensure deliverability.

Instructions

List all verified sender identities in your SendGrid account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for the 'list_verified_senders' tool within the handleToolCall switch statement. It calls service.getVerifiedSenders() and formats the response as JSON text.
    case 'list_verified_senders':
      const senders = await service.getVerifiedSenders();
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(senders, null, 2)
        }]
      };
  • The input schema and metadata definition for the 'list_verified_senders' tool in the getToolDefinitions array.
    {
      name: 'list_verified_senders',
      description: 'List all verified sender identities in your SendGrid account',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      }
    },
  • The core helper method in SendGridService that retrieves verified senders from the SendGrid API endpoint /v3/verified_senders.
    async getVerifiedSenders() {
      const [response] = await this.client.request({
        method: 'GET',
        url: '/v3/verified_senders'
      });
      return response.body;
    }
  • src/index.ts:42-46 (registration)
    MCP server registration for listing tools, which includes 'list_verified_senders' via getToolDefinitions.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: getToolDefinitions(sendGridService)
      };
    });
  • src/index.ts:52-75 (registration)
    MCP server registration for tool calls, which routes to handleToolCall including the 'list_verified_senders' case.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      try {
        return await handleToolCall(sendGridService, request.params.name, request.params.arguments);
      } catch (error: any) {
        console.error('SendGrid Error:', error);
        
        // Handle SendGrid API errors
        if (error.response?.body?.errors) {
          throw new McpError(
            ErrorCode.InternalError,
            `SendGrid API Error: ${error.response.body.errors.map((e: { message: string }) => e.message).join(', ')}`
          );
        }
        
        // Handle other errors
        if (error instanceof Error) {
          throw new McpError(
            ErrorCode.InternalError,
            error.message
          );
        }
        
        throw new McpError(ErrorCode.InternalError, 'An unexpected error occurred');
      }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'List all' implies a read-only operation, it doesn't specify whether this requires authentication, has rate limits, returns paginated results, or what format the output takes. The description provides minimal behavioral context beyond the basic action.

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 that communicates the complete purpose without any wasted words. It's front-loaded with the core action and resource, making it immediately understandable to an agent scanning tool descriptions.

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

Completeness3/5

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

For a zero-parameter listing tool with no annotations and no output schema, the description provides adequate but minimal context. It specifies what's being listed and where, but doesn't address output format, authentication requirements, or potential limitations. Given the simplicity of the tool (no parameters, read-only operation), the description is complete enough for basic usage but lacks depth.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't mention parameters since none exist, maintaining focus on the tool's purpose. This meets the baseline expectation for zero-parameter tools.

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 specific action ('List all') and resource ('verified sender identities in your SendGrid account'). It distinguishes itself from sibling tools like list_contacts, list_templates, and list_contact_lists by specifying the exact type of entities being listed.

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. It doesn't mention prerequisites, context for usage, or differentiate from similar listing tools like list_contacts or list_templates. The agent must infer usage from the tool name alone.

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