Skip to main content
Glama

Deliveries Emails File

deliveries_emails_file

Retrieve the stored file for a specific email delivery by organisation and email ID, returning the redirect URL and status code without following the redirect.

Instructions

Get file of email. GET /organisations/{organisationId}/deliveries/emails/{emailId}/file

Answers 302 to the stored file; returns the {"redirect_url", "status_code"} envelope without following the redirect.

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_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
email_idYes
organisation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and usefully discloses the non-obvious redirect behavior: the endpoint answers 302 to the stored file and returns a JSON envelope without following the redirect. It does not cover authorization or error behavior, but the key runtime trait is captured.

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 front-loaded and efficient, using two sentences with no filler. The phrase 'Get file of email' is slightly awkward, and the endpoint path duplicates schema names, but the structure remains clear.

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 read endpoint with no output schema, the description covers the essential unusual behavior around redirects and the response envelope. The main remaining gap is that the parameters are not explained beyond their path placement.

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 should compensate by explaining organisation_id and email_id. Instead, it only repeats the parameter names inside the URL template without adding meaning, format, or sourcing guidance.

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 ('Get file of email') and includes the exact endpoint path. It is clear what the tool does, but it does not explicitly differentiate itself from siblings like deliveries_emails_show or deliveries_emails_events_image.

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 this tool versus alternatives such as deliveries_emails_show, deliveries_emails_events_image, or other file-retrieval siblings. The description also omits prerequisites or exclusions.

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