delete_segment
Delete a segment from your Resend account using its unique ID to clean up audience segments.
Instructions
Delete a segment by ID.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The resource ID |
Delete a segment from your Resend account using its unique ID to clean up audience segments.
Delete a segment by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The resource ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide destructiveHint=true and idempotentHint=true. The description reinforces the destructive nature but adds no additional behavioral context beyond what annotations convey.
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?
The description is a single sentence that conveys the purpose directly. No wasted words.
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?
For a simple tool with one parameter and no output schema, the description is largely sufficient. It could mention irreversibility, but annotations already imply destructive behavior.
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%. The single parameter 'id' has a clear description in the schema. The tool description adds no extra meaning beyond that.
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' and resource 'segment', with the input 'by ID'. It is specific and distinguishes from sibling tools like create_segment or list_segments.
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., other delete tools). The description does not provide context for prerequisites or exclusions.
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/helbertparanhos/resend-email-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server