Skip to main content
Glama
Garoth

SendGrid MCP Server

by Garoth

list_templates

Retrieve all email templates from your SendGrid account to manage and reuse them for email campaigns.

Instructions

List all email templates in your SendGrid account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_templates' tool call. It invokes service.listTemplates() and formats the response as a JSON string of template summaries.
    case 'list_templates':
      const templates = await service.listTemplates();
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(templates.map(t => ({
            id: t.id,
            name: t.name,
            generation: t.generation,
            updated_at: t.updated_at,
            versions: t.versions.length
          })), null, 2)
        }]
      };
  • Registration of the 'list_templates' tool in getToolDefinitions, including name, description, and input schema (empty object).
    {
      name: 'list_templates',
      description: 'List all email templates in your SendGrid account',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      }
    },
  • Input schema for the 'list_templates' tool: an empty object with no required properties.
    inputSchema: {
      type: 'object',
      properties: {},
      required: []
    }
  • Helper method in SendGridService that fetches the list of dynamic templates from the SendGrid API.
    async listTemplates(): Promise<SendGridTemplate[]> {
      const [response] = await this.client.request({
        method: 'GET',
        url: '/v3/templates',
        qs: {
          generations: 'dynamic'
        }
      });
      return ((response.body as { templates: SendGridTemplate[] }).templates || []);
    }
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 mention any constraints like pagination, rate limits, authentication needs, or what the return format looks like. This leaves significant gaps for a tool that interacts with an external API.

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 function without any fluff or redundancy. 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 complexity of listing resources from an external service (SendGrid), the description is incomplete. With no annotations and no output schema, it doesn't explain behavioral aspects like pagination, sorting, error handling, or response format. For a read operation in a production environment, this lacks necessary context for reliable use.

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 input schema has 0 parameters with 100% coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter details, and it correctly implies no filtering or options are required. Baseline is 4 for zero parameters, as the description aligns with the schema's emptiness.

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 email templates in your SendGrid account'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_template' (which retrieves a single template) or 'create_template' (which creates one), missing explicit sibling 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. It doesn't mention that 'get_template' is for retrieving a specific template by ID, or that this tool is for browsing all templates without filtering. No usage context or exclusions are provided.

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