Skip to main content
Glama

Deliveries Emails Events Image

deliveries_emails_events_image

Retrieve an email delivery event image by organisation, email, and event IDs; returns the redirect URL and status code without following it.

Instructions

Get an image of an email event. GET /organisations/{organisationId}/deliveries/emails/{emailId}/events/{deliverableEventId}/image

Answers 302 to the image; 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>",
      "deliverable_event_id": "<deliverable_event_id>"
    },
    "name": "deliveries_emails_events_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
email_idYes
organisation_idYes
deliverable_event_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it discloses that the endpoint answers 302 and that the tool deliberately does not follow the redirect, returning only a {redirect_url, status_code} envelope. That is exactly the kind of non-obvious behavior an agent needs. It omits auth/permission expectations and what happens when the event has no image.

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?

Two tight sentences: purpose first, then the behavioral caveat about redirects. Nothing is padded, though the doubled backticks around the return envelope are a formatting artifact rather than useful content.

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?

There is no output schema, and the description compensates by naming the returned fields (redirect_url, status_code) and explaining the non-follow behavior, which is the key thing to know for a redirecting image endpoint. Only the permission/auth dimension is left unaddressed.

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 coverage is 0%, so the description must compensate. The embedded path template maps each of the three required parameters to a URL segment, which clarifies what each identifier refers to in context. However, it adds no detail on identifier formats or where a deliverable_event_id comes from, leaving real semantic gaps.

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 concrete verb and resource ('Get an image of an email event') and reinforcing the exact HTTP path makes the target unmistakable. It does not explicitly contrast itself with the close sibling deliveries_ebills_events_image or with deliveries_emails_events, so it falls short of full sibling differentiation.

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 explicit when-to-use statement, no prerequisites, and no mention of the alternative event-detail tool (deliveries_emails_events) that an agent might choose instead if it wanted metadata rather than an image. Usage is only inferable from the one-line purpose.

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