Skip to main content
Glama

Deliveries Emails Delete

deliveries_emails_delete

Deletes a specific delivery email from an organisation using organisation and email IDs, removing the email record through the Pingen API.

Instructions

Delete an email. DELETE /organisations/{organisationId}/deliveries/emails/{emailId}

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": {
      "organisation_id": "<organisation_id>",
      "email_id": "<email_id>"
    },
    "name": "deliveries_emails_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
email_idYes
organisation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It states "Delete" but does not disclose destructive effects, reversibility, required permissions, side effects, or what happens to related records. The operation is identifiable as destructive, but important behavioral context is missing.

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 two short, front-loaded statements with no wasted wording. "Delete an email" comes first, followed by the exact endpoint path, so the agent can quickly understand the operation.

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

Completeness2/5

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

For a destructive delete tool with no annotations, no output schema, and 0% parameter description coverage, the definition is materially incomplete. It omits deletion semantics, permission requirements, side effects, and meaningful parameter explanations, so an agent cannot confidently call it without outside knowledge.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain the two required parameters. It only shows them embedded in the URL template, which clarifies that they are path parameters but not what they represent, their format, or any constraints. This is insufficient for a schema with no parameter descriptions.

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 states a specific verb and resource: "Delete an email." The endpoint path reinforces that this removes an email at a given organisation/email identifier. It does not differentiate from the sibling `deliveries_emails_cancel`, so the purpose is clear but not sibling-explicit.

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 on when to use deletion versus cancellation or any other sibling operation. It also gives no prerequisites, warnings, or conditions for use, leaving the agent to infer that this is a destructive operation.

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