Skip to main content
Glama
deyikong

SendGrid MCP Server

by deyikong

Create Email List

create_email_list

Create a new email list in your SendGrid account to organize contacts for targeted email marketing campaigns.

Instructions

Create a new email list in your SendGrid account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the email list

Implementation Reference

  • Handler function that checks read-only mode, makes a POST request to SendGrid API to create the email list with the given name, and returns the JSON response.
    handler: async ({ name }: { name: string }): Promise<ToolResult> => {
      const readOnlyCheck = checkReadOnlyMode();
      if (readOnlyCheck.blocked) {
        return { content: [{ type: "text", text: readOnlyCheck.message! }] };
      }
      
      const result = await makeRequest("https://api.sendgrid.com/v3/marketing/lists", {
        method: "POST",
        body: JSON.stringify({ name }),
      });
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    },
  • Tool configuration including title, description, and Zod input schema for the 'name' parameter.
    config: {
      title: "Create Email List",
      description: "Create a new email list in your SendGrid account",
      inputSchema: {
        name: z.string().describe("Name of the email list"),
      },
    },
  • src/index.ts:21-23 (registration)
    Registers all tools, including 'create_email_list', to the MCP server via a loop over the allTools object.
    for (const [name, tool] of Object.entries(allTools)) {
      server.registerTool(name, tool.config as any, tool.handler as any);
    }
  • Aggregates all tool objects from modular files, including contactTools containing 'create_email_list', into a single allTools export.
    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?

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Create' implies a write operation, it doesn't specify what happens on success/failure, whether the list becomes immediately usable, if there are rate limits, or what permissions are required. 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, 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, what happens on failure, or any behavioral nuances. The agent would need to guess about the operation's outcome and error conditions.

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 description doesn't mention parameters, but with 100% schema description coverage and only one parameter ('name' with clear description), the schema fully documents the input requirements. For a single-parameter tool with excellent schema coverage, the description doesn't need to repeat parameter information, earning a baseline score of 4.

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 email list in your SendGrid account'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'create_contact' or 'create_sender', but the specificity of 'email list' provides inherent 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 like 'update_email_list' or 'list_email_lists'. There's no mention of prerequisites, constraints, or typical use cases, leaving the agent to infer usage context 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/deyikong/sendgrid-mcp'

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