get_delivery_operationCheck the saved result of a send or forward, including whether it succeeded, failed or has an uncertain outcome.
| Name | Required | Description | Default |
|---|---|---|---|
| accountId | Yes | ||
| operationId | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": false,
+ "properties": {
+ "data": {
+ "additionalProperties": true,
+ "properties": {
+ "accountId": {
+ "type": "string"
+ },
+ "error": {
+ "additionalProperties": false,
+ "properties": {
+ "code": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "code"
+ ],
+ "type": "object"
+ },
+ "kind": {
+ "type": "string"
+ },
+ "operationId": {
+ "type": "string"
+ },
+ "result": {
+ "additionalProperties": true,
+ "properties": {
+ "id": {
+ "type": "string"
+ },
+ "threadId": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "threadId"
+ ],
+ "type": "object"
+ },
+ "status": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "operationId",
+ "accountId",
+ "kind",
+ "status"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "data"
+ ],
+ "type": "object"
+}Input schema / properties / accountId / maxLengthAdded value: +512Input schema / properties / operationId / maxLengthAdded value: +512Input schema / $schemaPrevious value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"Input schema / properties / accountId / maxLengthRemoved value: -512Input schema / properties / operationId / maxLengthRemoved value: -512Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish that this is a read-only, non-destructive, closed-world operation. The description adds useful behavioral context by saying the result is saved and can report success, failure, or an uncertain outcome.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no wasted wording. It immediately communicates the core purpose and the possible outcome states.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return-value details need not be repeated in the description, and annotations cover the safety profile. Still, the description lacks parameter guidance and explicit usage conditions, leaving gaps for an agent invoking the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and both required parameters are undocumented in the schema. The description mentions checking a send or forward result but does not explain accountId or operationId, so it does not compensate for the parameter documentation gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb-resource pair: checking the saved result of a send or forward. It clearly distinguishes this status-checking operation from sending tools, though it does not explicitly name related siblings such as preview_send or send_email.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It implies usage after a send or forward by referring to the saved result of those operations. However, it gives no explicit when-to-use guidance, prerequisites, or alternatives for checking operation status.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.