Delete Contact
delete_contactRemove specific contacts from your SendGrid contact list by providing their unique IDs.
Instructions
Delete contacts by IDs
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| contact_ids | Yes | Array of contact IDs to delete |
delete_contactRemove specific contacts from your SendGrid contact list by providing their unique IDs.
Delete contacts by IDs
| Name | Required | Description | Default |
|---|---|---|---|
| contact_ids | Yes | Array of contact IDs to delete |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and the description only states the action. It does not disclose whether the deletion is permanent, if related data (e.g., list memberships) are affected, or any other behavioral traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, front-loaded with key information. No filler, but could be slightly expanded without losing conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Sufficient for a simple operation with one parameter, but lacks behavioral context (e.g., irreversibility, impact on related data) that would fully inform an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description adds no meaning beyond what the schema provides—'by IDs' is redundant with the parameter description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (delete), the resource (contacts), and the scope (by IDs). It effectively distinguishes from sibling delete tools that target different resources.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives (e.g., removing contacts from lists). No prerequisites, consequences, or exclusions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/deyikong/sendgrid-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server