Skip to main content
Glama
Garoth

SendGrid MCP Server

by Garoth

delete_template

Remove a dynamic email template from SendGrid by specifying its template ID to manage your email marketing content.

Instructions

Delete a dynamic template from SendGrid

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
template_idYesID of the template to delete

Implementation Reference

  • Core implementation of the delete_template tool: sends a DELETE request to the SendGrid Templates API endpoint to delete the specified template.
    async deleteTemplate(templateId: string): Promise<void> {
      await this.client.request({
        method: 'DELETE',
        url: `/v3/templates/${templateId}`
      });
    }
  • Tool registration/definition including name, description, and input schema for delete_template.
    {
      name: 'delete_template',
      description: 'Delete a dynamic template from SendGrid',
      inputSchema: {
        type: 'object',
        properties: {
          template_id: {
            type: 'string',
            description: 'ID of the template to delete'
          }
        },
        required: ['template_id']
      }
    },
  • Dispatcher case in handleToolCall function that invokes the deleteTemplate service method and formats the response.
    case 'delete_template':
      await service.deleteTemplate(args.template_id);
      return { content: [{ type: 'text', text: `Template ${args.template_id} deleted successfully` }] };
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 action is destructive ('Delete'), but lacks details on permissions required, whether deletion is permanent or reversible, error handling, or side effects. 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 directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, 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?

For a destructive mutation tool with no annotations and no output schema, the description is insufficient. It doesn't cover behavioral aspects like permanence, permissions, or error responses, nor does it reference related tools for context, leaving significant gaps in understanding.

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?

The schema description coverage is 100%, with the single parameter 'template_id' fully documented in the schema. The description doesn't add any parameter-specific information beyond what the schema provides, such as format examples or sourcing guidance, so it meets the baseline for high schema coverage.

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 dynamic template from SendGrid'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'delete_contacts' or 'delete_list' beyond specifying the resource type, which prevents a perfect score.

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 the template ID from 'list_templates' or 'get_template'), exclusions, or related tools for creation ('create_template') or retrieval ('get_template'), leaving usage context unclear.

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