Skip to main content
Glama

etsy_shipping_profile_destination_create

Create a destination entry for an Etsy shipping profile, specifying primary and secondary costs, region, carrier, and delivery days.

Instructions

Create a destination entry for a shipping profile

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
shop_idYes
mail_classNo
primary_costYes
secondary_costYes
max_delivery_daysNo
min_delivery_daysNo
destination_regionNo
shipping_carrier_idNo
shipping_profile_idYes
destination_country_isoNo
Behavior2/5

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

No annotations are present, so the description must disclose behavioral traits. It only states 'create', implying a write operation, but fails to mention any side effects, constraints, or required permissions. It does not describe what happens on success or error.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but lacks structure and fails to provide necessary details. It is not verbose, but the brevity comes at the cost of completeness.

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

Completeness1/5

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

Given the complexity of 10 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain the concept of a destination entry, the meaning of required vs optional fields, or what the tool returns upon creation.

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

Parameters1/5

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

Schema description coverage is 0%, meaning neither the schema nor the description explains any parameter. The description does not elaborate on the 10 parameters, including required fields like primary_cost and secondary_cost, leaving the agent without context for correct usage.

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 clearly states the action and resource: 'Create a destination entry for a shipping profile'. It uses a specific verb and resource, but does not differentiate from sibling tools like etsy_shipping_profile_destination_update or etsy_shipping_profile_destinations_list.

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?

No guidance is provided on when to use this tool versus alternatives like update or delete. There is no mention of prerequisites or context such as whether a shipping profile must already exist.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BusyBee3333/etsy-mcp-2026-complete'

If you have feedback or need assistance with the MCP directory API, please join our Discord server