Skip to main content
Glama

etsy_shop_shipping_profile_create

Create a new shipping profile for your Etsy shop by specifying origin country, costs, processing times, and delivery options.

Instructions

Create a shipping profile for a shop

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesProfile name
shop_idYes
mail_classNo
primary_costYesPrimary shipping cost
secondary_costYesAdditional item shipping cost
max_delivery_daysNo
min_delivery_daysNo
destination_regionNo
origin_country_isoYesISO country code of ship-from location
origin_postal_codeNo
max_processing_timeYes
min_processing_timeYes
shipping_carrier_idNo
processing_time_unitNo
destination_country_isoNo
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only says 'create', which implies mutation but lacks details on side effects, authentication requirements, or limits on profile creation. Minimal behavioral disclosure.

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?

Extremely short (one sentence), which is concise but at the cost of necessary detail. Could easily expand to include key parameters or usage context without becoming verbose.

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 15 parameters (7 required), no output schema, and low schema coverage, the description provides virtually no useful context for a complex creation tool. The agent lacks information to correctly populate parameters or understand the tool's effect.

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 only 27%, and the description adds no additional meaning for any of the 15 parameters. The agent must guess parameter roles beyond the sparse schema descriptions.

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?

Clearly states 'Create a shipping profile for a shop' with a specific verb and resource. However, it does not differentiate from related sibling tools like etsy_shop_shipping_profile_update or etsy_shipping_profile_destination_create, which could cause confusion.

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 on when to use this tool versus alternatives. With multiple shipping-related tools (create, update, delete, destinations), the description lacks context for appropriate invocation.

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