Skip to main content
Glama
Garoth

SendGrid MCP Server

by Garoth

list_contact_lists

Retrieve all contact lists from your SendGrid account to manage email marketing campaigns and audience segmentation.

Instructions

List all contact lists in your SendGrid account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function that executes the API call to retrieve all contact lists from SendGrid's /v3/marketing/lists endpoint.
    async listContactLists(): Promise<SendGridList[]> {
      const [response] = await this.client.request({
        method: 'GET',
        url: '/v3/marketing/lists'
      });
      return (response.body as { result: SendGridList[] }).result;
    }
  • Tool-specific handler in the main tool dispatcher that invokes the service method and formats the response as a JSON string.
    case 'list_contact_lists':
      const lists = await service.listContactLists();
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(lists.map(l => ({
            id: l.id,
            name: l.name,
            contact_count: l.contact_count
          })), null, 2)
        }]
      };
  • Tool registration including name, description, and input schema (no inputs required).
    {
      name: 'list_contact_lists',
      description: 'List all contact lists in your SendGrid account',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      }
    },
  • Input schema definition for the tool (empty object, no parameters required).
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      }
    },
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 it's a list operation but doesn't mention whether it's paginated, rate-limited, requires authentication, returns structured data, or has any side effects. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 any unnecessary words. It's appropriately sized and front-loaded, with zero wasted 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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the return value looks like (e.g., list format, fields included), pagination behavior, or error conditions. For a list operation in a context with multiple sibling list tools, more guidance is needed to help the agent use it correctly.

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 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter semantics, and it correctly doesn't mention any parameters, earning a baseline score of 4 for appropriate handling of a parameterless tool.

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 verb ('List') and resource ('all contact lists in your SendGrid account'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_contacts' or 'list_templates', which would require a 5.

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 'list_contacts' or 'get_contacts_by_list'. It lacks any context about use cases, prerequisites, or exclusions, leaving the agent to 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