Skip to main content
Glama
Sign In
SendGrid MCP Server

SendGrid MCP Server

by deyikong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete Template Version

delete_template_version
DestructiveIdempotent

Delete a specific version of an email template by supplying the template ID and version ID.

Instructions

Delete a specific version of a template

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "template_id": "<template_id>",
      "version_id": "<version_id>"
    },
    "name": "delete_template_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
version_idYesID of the version to delete
template_idYesID of the template

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed2 schema fields changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description aligns with the destructiveHint=true annotation and adds that only a specific version is affected, not the template itself. It does not add deeper behavioral context such as reversibility, permissions, or consequences for the parent template, but the annotations already cover destructive intent and idempotency.

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 with no filler. It front-loads the action and the specific resource, making it immediately actionable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-string-parameter destructive operation, the description plus annotations and full schema coverage are largely sufficient. It lacks explicit guidance on alternatives, but the task is simple enough that an agent can invoke it confidently from the given information.

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?

Schema description coverage is 100%, and both parameters, template_id and version_id, already have clear schema descriptions. The tool description does not add any additional parameter meaning beyond what the schema already provides, so the baseline score applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb, ‘delete’, a clear resource, ‘a specific version of a template’, and distinguishes this from deleting the entire template. The sibling tool list includes delete_template, so the version-specific wording helps disambiguate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase ‘a specific version of a template’ clearly implies this tool is for version-scoped deletion, and the sibling list includes delete_template for the alternative. However, it does not explicitly state when not to use this tool or direct the agent to delete_template for whole-template deletion.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools