Skip to main content
Glama
Sign In
etsy-clean-mcp

etsy-clean-mcp

by phobicdotno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

add_tracking

Add tracking to an Etsy order and mark it shipped, with buyer email notification. Set confirm=false to preview before sending.

Instructions

Add tracking to an order and mark it shipped. Etsy emails the buyer. confirm=false previews.

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": {
      "receipt_id": "<receipt_id>",
      "tracking_code": "<tracking_code>",
      "carrier_name": "<carrier_name>"
    },
    "name": "add_tracking"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNofalse (default) only returns a preview of the request. true sends it.
send_bccNoAlso send the shipping email to you.
receipt_idYesReceipt id.
carrier_nameYesCarrier name, e.g. 'posten', 'usps', 'dhl'.
tracking_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description adds value beyond them by disclosing the external side effect (Etsy emails the buyer) and the confirm=false preview mode that only returns a preview without sending the request. It stops short of stating failure conditions, idempotency, or required order state, so not a 5.

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?

Three compact sentences: action, side effect, preview control. Purpose is front-loaded and every clause carries useful information.

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 5-parameter mutation tool with no output schema, the description covers what it does, the external notification, and the safe preview path. It lacks only edge-case behavior such as invalid receipt states or error handling.

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 80%, so the baseline is 3; the description adds relevant meaning by tying confirm=false to a preview call and by clarifying that an email is sent to the buyer, which gives context for send_bcc. The remaining parameters are documented in the schema itself.

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: adds tracking to an order and marks it shipped, plus the Etsy buyer-email side effect. This clearly separates it from read-oriented siblings such as get_receipt and from update_inventory.

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

Usage Guidelines3/5

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

Usage is implied by 'order' and 'shipped', and confirm=false preview guidance gives a procedural hint, but there is no explicit when-to-use versus not, nor prerequisites such as the receipt being unshipped.

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

Deploy Server

Other Tools