Skip to main content
Glama

Email: Delete draft

email_delete_draft
Destructive

Discard one exact draft. draft_id comes from draft list/create; destructive.

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": {
      "draft_id": "<draft_id>"
    },
    "name": "email_delete_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_idYesExact draft ID returned by email_list_drafts/email_create_draft; never use subject or email_id as draft_id.
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already establish that this is a destructive, non-read-only operation, and the description's "destructive" warning largely repeats that information. It adds that exactly one draft is discarded, but does not clarify permanence, recoverability, or any resulting behavior.

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 definition front-loads the operation and scope, then gives the ID source and risk in a very compact form. There is no filler, and the slight repetition of the destructive annotation does not create meaningful bloat.

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-parameter deletion tool, the description, complete schema, and safety annotations provide enough information for normal selection and invocation. It would be more complete with recovery or permanence details and an explicit alternative, while the absence of an output schema leaves the success result unspecified.

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%, so the baseline is 3. The description's draft_id provenance is useful but already covered more precisely by the schema, which also prohibits subject or email_id and fully explains account_id selection.

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?

"Discard one exact draft" clearly states the action, resource, and single-item scope. It does not explicitly differentiate the tool from siblings such as email_trash or email_update_draft.

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

Usage Guidelines4/5

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

The note that draft_id comes from draft list/create provides concrete guidance on obtaining the required identifier before invocation. However, there is no explicit when-not guidance or pointer to an alternative for sent messages, drafts that should be edited, or other deletion scenarios.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.