Skip to main content
Glama

Order: Send Tracking Email

send_buyer_tracking_notification
Destructive

[Order] [What it does] Asynchronously requests a Shopify fulfillment tracking notification for the buyer of one owned order; Shopify only. [When to use] Use when the merchant wants Shopify to notify the buyer about tracking for fulfilled items that already have tracking information. [When not to use] To fulfill items or synchronize tracking to the seller store, use sync_existing_tracking_numbers_to_store first. This tool does not apply to non-Shopify platforms. [How to use]

  • Copy one exact dsers_order_id from get_order after checking the fulfilled items and tracking information. The request is order-wide and cannot select a subset of line items.

  • A successful response contains only message: it means DSers accepted an asynchronous notification request, not that Shopify sent it or the buyer received it. Shopify may suppress an identical recent update.

  • Send once, never auto-retried. If the outcome is unknown, check the Shopify order and buyer notification history before deciding what to do; get_order can confirm order and tracking prerequisites but cannot confirm notification delivery. [Side effects] May send an external tracking notification to the buyer. [Confirmation] Required, never skippable: show the exact order, eligible fulfilled items, and tracking information, and state that this may contact the buyer. [Follow-up] After acceptance, check the Shopify order and buyer notification history later; if rejected, report the error and stop.

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": {
      "dsers_order_id": "<dsers_order_id>"
    },
    "name": "send_buyer_tracking_notification"
  }
}

Input Schema

NameRequiredDescriptionDefault
dsers_order_idYesExactly one DSers order ID. Copy from get_order response. Required.

Output Schema

NameRequiredDescriptionDefault
messageYesOutcome and safe next step
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, openWorldHint=true and idempotentHint=false, but the description goes well beyond them: it discloses asynchronous acceptance semantics ('only `message`', not proof of sending), possible Shopify suppression of duplicate updates, the no-auto-retry policy, the required confirmation step, and that an external buyer contact may occur.

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?

Front-loaded with the action and organized under bracketed headings that make scanning easy; every section (prerequisites, side effects, confirmation, follow-up) carries non-redundant information. The labeled structure is slightly verbose but earns its space.

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

Completeness5/5

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

For a single-parameter, side-effecting notification tool with an output schema, the description covers prerequisites, irreversibility of the request, how to interpret the terse success response, confirmation requirements, and failure follow-up. Nothing an agent needs to call it safely is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents `dsers_order_id`; the description nonetheless adds operational meaning — copy exactly one ID from `get_order`, and the request is order-wide with no line-item subsetting. That constraint is not expressible in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — asynchronously request a Shopify fulfillment tracking notification for the buyer of one owned order — plus the platform scope ('Shopify only'). This distinguishes it cleanly from sibling sync tools that move tracking data rather than notify the buyer.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Has explicit 'When to use' (fulfilled items that already have tracking), explicit 'When not to use' (use `sync_existing_tracking_numbers_to_store` to fulfill or sync tracking to the seller store), and a platform exclusion for non-Shopify. The prerequisite chain via `get_order` is spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.