Skip to main content
Glama

etsy_shop_production_partner_create

Create a new production partner for your Etsy shop by specifying its name, location, and whether it is unlisted.

Instructions

Create a new production partner for a shop

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
shop_idYes
locationYesCity/region where partner is located
is_unlistedNoWhether the partner is unlisted
partner_nameYesName of the production partner
Behavior2/5

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

No annotations are present, so the description carries full responsibility for behavioral disclosure. It only states 'Create', without mentioning side effects, permissions, idempotency, or return behavior. A mutation tool requires more transparency.

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?

The description is a single, concise sentence without any unnecessary words. It is front-loaded with the action and resource.

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

Completeness2/5

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

Given the lack of annotations and output schema, and the presence of sibling CRUD tools, the description is too brief. It does not explain what a production partner is, prerequisites (e.g., shop existence), or the return format, leaving significant gaps for the agent.

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

Parameters3/5

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

The input schema covers 75% of parameters with descriptions (3 out of 4). The tool description adds no extra parameter context, but with high coverage, a score of 3 is appropriate as the schema does the heavy lifting.

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?

Clearly states 'Create a new production partner for a shop', with specific verb and resource. The name and description distinguish it from sibling tools like etsy_shop_production_partner_delete, etsy_shop_production_partners_list, and etsy_shop_production_partner_update.

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. No prerequisites or context are provided, leaving the agent to infer usage from the tool name alone.

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