Skip to main content
Glama
Garoth

SendGrid MCP Server

by Garoth

delete_list

Remove a contact list from SendGrid's email marketing platform by specifying its ID to manage subscriber data.

Instructions

Delete a contact list from SendGrid

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesID of the contact list to delete

Implementation Reference

  • The core handler function in SendGridService that performs the API call to delete a marketing contact list by its ID.
    async deleteList(listId: string): Promise<void> {
      await this.client.request({
        method: 'DELETE',
        url: `/v3/marketing/lists/${listId}`
      });
    }
  • The tool registration definition including name, description, and input schema for the 'delete_list' tool in getToolDefinitions.
    {
      name: 'delete_list',
      description: 'Delete a contact list from SendGrid',
      inputSchema: {
        type: 'object',
        properties: {
          list_id: {
            type: 'string',
            description: 'ID of the contact list to delete'
          }
        },
        required: ['list_id']
      }
    },
  • The switch case handler in handleToolCall that invokes the service.deleteList method and returns a success message.
    case 'delete_list':
      await service.deleteList(args.list_id);
      return { content: [{ type: 'text', text: `Contact list ${args.list_id} deleted successfully` }] };
  • The input schema definition for the 'delete_list' tool, specifying the required 'list_id' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        list_id: {
          type: 'string',
          description: 'ID of the contact list to delete'
        }
      },
      required: ['list_id']
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 deletes a contact list, implying a destructive mutation, but doesn't cover critical aspects like whether deletion is permanent, requires specific permissions, has side effects (e.g., on associated contacts), or returns confirmation. This is inadequate for a mutation tool with zero annotation coverage.

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 that efficiently conveys the core action without any wasted words. It's front-loaded with the essential information ('Delete a contact list from SendGrid'), making it highly concise and well-structured for quick comprehension.

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 the tool's destructive nature, lack of annotations, and no output schema, the description is insufficiently complete. It doesn't address behavioral risks, return values, or usage context, leaving significant gaps for an agent to safely and effectively invoke this mutation tool.

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 single parameter 'list_id' fully documented in the schema as 'ID of the contact list to delete'. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage without compensating 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 clearly states the action ('Delete') and resource ('a contact list from SendGrid'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'delete_contacts' or 'delete_template', which would require specifying it's for contact lists specifically versus other deletable resources.

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., needing an existing list), exclusions (e.g., not for deleting contacts), or compare it to siblings like 'delete_contacts' or 'remove_contacts_from_list', leaving the agent to infer usage from context 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