Skip to main content
Glama
Garoth

SendGrid MCP Server

by Garoth

create_contact_list

Create a new contact list in SendGrid to organize email recipients for targeted marketing campaigns.

Instructions

Create a new contact list in SendGrid

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the contact list

Implementation Reference

  • Handler logic for the 'create_contact_list' tool within the handleToolCall switch statement. It invokes SendGridService.createList with the input 'name' argument and returns a formatted success response including the new list ID.
    case 'create_contact_list':
      const list = await service.createList(args.name);
      return { content: [{ type: 'text', text: `Contact list "${args.name}" created with ID: ${list.id}` }] };
  • Tool definition including name, description, and input schema requiring a 'name' string parameter.
    {
      name: 'create_contact_list',
      description: 'Create a new contact list in SendGrid',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Name of the contact list'
          }
        },
        required: ['name']
      }
    },
  • SendGridService method that performs the actual API call to create a new contact list using SendGrid's Marketing Lists endpoint.
    async createList(name: string): Promise<SendGridList> {
      const [response] = await this.client.request({
        method: 'POST',
        url: '/v3/marketing/lists',
        body: { name }
      });
      return response.body as SendGridList;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates a contact list but doesn't mention what happens after creation (e.g., whether it returns an ID, if there are rate limits, permission requirements, or error conditions). This leaves significant gaps for a mutation tool.

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 states the core purpose without unnecessary words. It's appropriately sized for a simple creation tool and front-loads the essential information.

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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns (e.g., a list ID), error handling, or behavioral constraints. Given the complexity of creating a resource in an external service, 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?

The schema description coverage is 100%, with the single parameter 'name' clearly documented in the schema. The description doesn't add any additional meaning about the parameter beyond what the schema provides, so it meets 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 ('Create') and resource ('new contact list in SendGrid'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'list_contact_lists' or 'delete_list' beyond the obvious creation vs. listing/deletion 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. There's no mention of prerequisites (e.g., needing a SendGrid account), when not to use it (e.g., for updating existing lists), or how it relates to sibling tools like 'add_contacts_to_list' or 'list_contact_lists'.

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