Skip to main content
Glama
Garoth

SendGrid MCP Server

by Garoth

list_suppression_groups

Retrieve all unsubscribe groups to manage email recipients who opt out of specific email categories in SendGrid.

Instructions

List all unsubscribe groups in your SendGrid account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool handler for 'list_suppression_groups' that calls the service to fetch groups and returns them as JSON text.
    case 'list_suppression_groups':
      const groups = await service.getSuppressionGroups();
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(groups, null, 2)
        }]
      };
  • Registration of the 'list_suppression_groups' tool in getToolDefinitions, including name, description, and empty input schema.
    {
      name: 'list_suppression_groups',
      description: 'List all unsubscribe groups in your SendGrid account',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      }
    },
  • Service helper method getSuppressionGroups() that performs the API call to SendGrid's /v3/asm/groups endpoint to retrieve suppression groups.
      const [response] = await this.client.request({
        method: 'GET',
        url: '/v3/asm/groups'
      });
      return response.body;
    }
  • Input schema for the tool: empty object with no required properties.
    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, implying read-only behavior, but doesn't cover aspects like pagination, rate limits, authentication needs, or what the output looks like. This is a significant gap for a 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 directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy 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 the lack of annotations and output schema, the description is incomplete. It doesn't explain behavioral traits like response format, pagination, or error handling, which are crucial for a list operation. The simplicity of 0 parameters doesn't compensate for these gaps.

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, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter details, but this is appropriate given the lack of parameters, earning a baseline score of 4 for not introducing confusion.

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 ('unsubscribe groups in your SendGrid account'), making the purpose specific and understandable. It doesn't explicitly differentiate from sibling tools like 'list_contact_lists' or 'list_templates', but the resource specificity helps distinguish it.

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, context for usage, or comparisons to sibling tools like 'list_contact_lists' or 'list_contacts', leaving the agent without usage direction.

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