Skip to main content
Glama
Sign In
SendGrid MCP Server

SendGrid MCP Server

by deyikong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete Contact

delete_contact
DestructiveIdempotent

Remove contacts from your SendGrid lists by providing their IDs. Cleans up your audience by deleting specified entries.

Instructions

Delete contacts by IDs

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": {
      "contact_ids": "<contact_ids>"
    },
    "name": "delete_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
contact_idsYesArray of contact IDs to delete

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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description aligns by stating 'Delete.' It adds the 'by IDs' scoping but does not disclose irreversibility, cascading effects, or behavior on nonexistent IDs. The description does not contradict the annotations, so a neutral score is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, front-loaded, and free of filler. It is slightly redundant with the title, but for a one-parameter tool this brevity is still appropriate.

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, one-parameter destructive operation, the description plus annotations and full schema coverage provide enough information for an agent to select and invoke the tool correctly. It does not describe the response format, but that is a minor gap given the tool's simplicity.

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 coverage is 100%; the single parameter contact_ids is already described as 'Array of contact IDs to delete.' The description's 'by IDs' reinforces that meaning but adds no substantive information beyond the schema, so the baseline of 3 applies.

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 uses a specific verb ('Delete'), identifies the resource ('contacts'), and specifies selection by IDs, making the operation clear. It is semantically distinguishable from related sibling tools like create_contact or get_contact, though it does not explicitly differentiate itself from remove_contact_from_lists.

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?

There is no guidance about when to use this tool versus alternatives such as remove_contact_from_lists or update_contact, nor any mention of prerequisites or caveats. The only usage signal is implied by the name and description, not explicit.

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