SenderKit

Get Message

senderkit_messages_get

Read-only

Fetch full details and delivery status for a single message by ID — check whether a specific email or SMS was delivered, bounced, or failed.

Input Schema

Name	Required	Description	Default
`id`	Yes	Public message id (e.g. "msg_…").
`context`	Yes	Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."

Output Schema

Name	Required	Description
`vars`	Yes	Template variables supplied at send time.
`error`	Yes	Provider/bounce error message, or null.
`status`	Yes	Lifecycle status. failed = bounce or provider error (see error/timeline); suppressed = never attempted (address invalid or already suppressed); blocked = halted by automated content safety checks.
`channel`	Yes	Delivery channel.
`livemode`	Yes	Whether the message was created in live mode.
`metadata`	Yes	Caller-supplied metadata (scalar values) attached at send time.
`openedAt`	Yes	First reported email open (open tracking), or null.
`provider`	Yes	Provider that handled (or is handling) delivery, or null before dispatch.
`publicId`	Yes	Public message id (e.g. "msg_…") — the id senderkit_messages_get and senderkit_cancel_message take.
`timeline`	Yes	Lifecycle events, oldest first.
`clickedAt`	Yes	First reported link click (click tracking), or null.
`createdAt`	Yes	When the message was created.
`latencyMs`	Yes	Provider round-trip time in milliseconds, or null.
`recipient`	Yes	Recipient address / number / token as supplied.
`interpolate`	Yes	Raw sends only: whether server-side variable substitution ran.
`scheduledAt`	Yes	Deliver-at time for a scheduled send, or null for an immediate one.
`fromOverride`	Yes	Per-message From address override (email), or null.
`templateSlug`	Yes	Template the message was sent from, or null for a raw send.
`pinnedVersion`	Yes	Template version pinned by the caller, or null.
`idempotencyKey`	Yes	Caller-supplied idempotency key, or null.
`fromNameOverride`	Yes	Per-message From display-name override (email), or null.
`providerMessageId`	Yes	The provider's own id for this message, or null.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only that the payload includes delivery status values (delivered/bounced/failed); it says nothing about behavior on a missing/invalid ID, auth requirements, or rate limits, and an output schema is present to cover returns.

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?

A single front-loaded sentence with zero filler: the verb, resource, keying parameter, and the motivating outcome all appear before the em-dash clause. Nothing could be removed without losing meaning.

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 two-parameter read-only lookup with 100% schema coverage, full annotations, and an output schema, the description supplies enough to call the tool correctly. The one minor gap is behavior on a non-existent or inaccessible message ID, which the agent cannot infer from any supplied field.

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%: the 'id' format ("msg_…") and the mandatory analytics 'context' wording are fully documented in the schema. The description adds no syntax, format, or constraint information beyond that, so the baseline of 3 applies.

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 gives a specific verb and resource ('Fetch full details and delivery status for a single message by ID'), and the singular 'single message' implicitly separates it from the sibling senderkit_messages_list. It stops short of explicitly naming that sibling or senderkit_inbound_messages_get, so differentiation requires the agent to infer from the name.

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?

It states a clear use case — check whether a specific email or SMS was delivered, bounced, or failed — which tells the agent when this tool applies. It offers no exclusions or named alternatives (e.g. 'use messages_list to discover IDs first'), so routing decisions against siblings remain partly inferred.

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

All SenderKit tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.