Skip to main content
Glama
Garoth

SendGrid MCP Server

by Garoth

add_contacts_to_list

Add email addresses to a SendGrid contact list for email marketing campaigns. Specify the list ID and email array to manage subscriber groups.

Instructions

Add contacts to an existing SendGrid list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesID of the contact list
emailsYesArray of email addresses to add to the list

Implementation Reference

  • Core handler function that implements adding contacts to a SendGrid marketing list by updating contacts with the list_ids.
    async addContactsToList(listId: string, contactEmails: string[]) {
      const [response] = await this.client.request({
        method: 'PUT',
        url: '/v3/marketing/contacts',
        body: {
          list_ids: [listId],
          contacts: contactEmails.map(email => ({ email }))
        }
      });
      return response;
    }
  • Input schema defining parameters list_id and emails for the add_contacts_to_list tool.
    inputSchema: {
      type: 'object',
      properties: {
        list_id: {
          type: 'string',
          description: 'ID of the contact list'
        },
        emails: {
          type: 'array',
          items: {
            type: 'string'
          },
          description: 'Array of email addresses to add to the list'
        }
      },
      required: ['list_id', 'emails']
    }
  • Tool definition and registration within the getToolDefinitions array.
    {
      name: 'add_contacts_to_list',
      description: 'Add contacts to an existing SendGrid list',
      inputSchema: {
        type: 'object',
        properties: {
          list_id: {
            type: 'string',
            description: 'ID of the contact list'
          },
          emails: {
            type: 'array',
            items: {
              type: 'string'
            },
            description: 'Array of email addresses to add to the list'
          }
        },
        required: ['list_id', 'emails']
      }
    },
  • Dispatcher case in handleToolCall that invokes the service handler and formats the response.
    case 'add_contacts_to_list':
      await service.addContactsToList(args.list_id, args.emails);
      return { content: [{ type: 'text', text: `Added ${args.emails.length} contacts to list ${args.list_id}` }] };
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 for behavioral disclosure. It states the action ('Add contacts') but doesn't cover critical aspects like whether this requires specific permissions, how duplicates are handled, rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with zero wasted information, making it easy for an agent to parse quickly.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks information on behavioral traits (e.g., error handling, side effects), usage context, and expected outcomes, which are crucial for an agent to invoke it correctly in a real-world scenario.

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 both parameters ('list_id' and 'emails') clearly documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints, meeting the baseline for high schema coverage.

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 ('Add contacts') and target resource ('to an existing SendGrid list'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from sibling tools like 'add_contact' (which might add individual contacts) or 'remove_contacts_from_list' (the inverse operation), missing explicit differentiation.

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 (e.g., list must exist), exclusions (e.g., cannot add duplicates), or compare to siblings like 'add_contact' or 'send_to_list', leaving the agent with no contextual usage information.

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