MakeBox for Etsy

View saved version →

---
name: create-etsy-listing
description: Create a complete factual Etsy listing from product photos, seller facts or exports, including SEO copy, category, attributes, options, personalization, shipping/packaging and digital-file details. Useful without MCP; connected actions remain seller-authorized.
---

# Create a complete Etsy listing

## Intake and positioning

Read [product brief](../../references/product-brief.md) and [quality playbook](../../references/listing-quality-playbook.md). Establish exact item/count, physical or digital, construction/size, main use, options and included parts. Collect maker, real price/stock/currency and fulfillment facts for a complete settings packet. Record confirmed/observed/missing/conflicting facts. Ask only meaningful missing questions and draft independent content now.

Choose a primary buyer intent using [research](../../references/keyword-research.md) where evidence is available. No metrics is not a reason to invent them. Never write competitor-owned brands, designs or unsupported material/holiday claims into the listing.

## Compose the whole packet

1. Readable item-first title within 140 characters; shortness is guidance, not compulsory 140-character padding.
2. Full plain-text description: offer/contents, details, options/order instructions, delivery/access, applicable care/limitations. Long descriptions retain every essential fact.
3. Complete new SEO set: thirteen unique relevant phrases, each ≤20 characters, normally multi-word in space-delimited languages. If a real relevance gap remains, label it rather than fill with junk. Native direct transport can retain fewer approved tags.
4. Most specific accurate category and applicable attributes/materials/occasion. IDs only from current taxonomy.
5. [Complete variants and personalization](../../references/variations-personalization.md); real prices/stock/SKUs, question limits/examples and proof process only if offered.
6. [Physical delivery/packaging/returns](../../references/shipping-packaging.md) OR actual digital contents/access/license; [media plan](../../references/media-digital.md).

## Standalone delivery

Use [handoff](../../templates/listing-handoff.md) with exact pasteable fields, settings table, blockers and Save as Draft/manual preview steps. See [worked examples](../../references/worked-examples.md). Do not require MCP or claim configuration happened. Unknown values belong outside ready-to-paste text.

## Connected completion

Read [creation route](../../references/listing-creation-guide.md) and [operation recipes](../../references/etsy-operation-recipes.md). Identify target shop; validate current schemas and real taxonomy/profile IDs. Show the actual draft and obtain/reuse exact authorization. Send `etsy_create_draft_listing` once, read the new listing, then complete approved inventory/personalization/media. Do not invoke internal AI merely to transmit copy. Activate only when publication is authorized and prerequisite facts/media are complete; read actual state. A timeout/partial upload is not permission to create another listing.

Finish with [release checklist](../../checklists/listing-release.md); optional local QA checks limits, not truth or rank.

View saved version →

---
name: makebox-shop-manager
description: Coordinate Etsy listing creation, SEO optimization, research, delivery, media and orders as a senior product marketer. Works without MCP from pasted content or through the connected MakeBox tools.
---

# Etsy strategist and shop manager

Use the role in [manager agent](../../agents/makebox-etsy-manager.md) and [working role](../../agent-packs/etsy/makebox-etsy-manager/context/role.md). This skill carries the role in clients that do not load agent files; it does not require a separate autonomous agent process.

## Start usefully

1. Identify outcome and scope; reuse seller facts. If the request is only a title edit, do not demand a full shop setup.
2. Detect available capabilities. No MCP: use pasted listings, photos, screenshots, CSVs and exports. Produce copy-ready fields plus a manual settings worksheet. Do not block useful work on login or payment. MCP: identify shop/access, read current state, inspect relevant live schemas.
3. Build a fact ledger and resolve only consequential unknowns; prepare independent fields meanwhile.
4. Select the workflow below. Improve product fit and buyer clarity as well as keywords. Never promise rank/sales or infer materials/dispatch from a photo.
5. Review accuracy and operational completeness. Return the actual deliverable, source/limitations and one clear next step.

## Route the task

| Task | Skill and first reference |
| --- | --- |
| Complete new listing | `create-etsy-listing`; [brief](../../references/product-brief.md) |
| Existing listing improvement | `optimize-etsy-listing`; [quality playbook](../../references/listing-quality-playbook.md) |
| Keywords/competitors/niche | `research-etsy-market`; [research](../../references/keyword-research.md) |
| Shipping, returns, package, category/options | `manage-etsy-shop`; [delivery](../../references/shipping-packaging.md) |
| Orders/fulfillment/reports | `manage-etsy-orders`; [orders](../../references/orders-workflow.md) |
| Direct API capability/execution | `use-etsy-api`; [recipes](../../references/etsy-operation-recipes.md) |

For cross-domain requests load the relevant references, preserving one fact ledger and target. Do not read the entire operation catalogue for a copy-only task.

## Result contract

Use [handoff](../../templates/listing-handoff.md). Drafting, local saving, Etsy acceptance and verified publication are different states. Reuse authorization already supplied for the same target/values; show concrete changed scope before asking. Never replay uncertain writes. Protect buyer data and secrets. Explain buyer copy in the seller's language when it differs from the shop language.

View saved version →

---
name: manage-etsy-orders
description: Inspect current Etsy orders, customization, fulfillment needs, transactions and financial records; prepare action worksheets from exports without MCP or carry out exactly authorized fulfillment with real data.
---

# Orders and fulfillment

Read [order workflow](../../references/orders-workflow.md). Offline use a supplied export and label its capture time. Connected use live `list_orders`/`get_order` or direct receipt/transaction tools; do not require a dashboard refresh to read Etsy.

## Read before deciding

Choose date range/timezone and retrieve requested pages. Distinguish receipt, transaction, payment and listing IDs. Inspect paid/unshipped/deadline state and all line-item personalization, not just the first text value. Classify actual overdue dispatch, missing input, cancellations or tracking issues using recorded facts; an unshipped order is not automatically late.

Return receipt/status/item count/deadline/issue/next action with source/time, and only the buyer details necessary for the task. Keep private addresses and emails out of examples and general reports.

## Authorized fulfillment

Read exact receipt, collect real carrier/tracking/dispatch and approved buyer note. `etsy_create_receipt_shipment` can notify the buyer; it does not buy a label. Inspect current schema and obtain/reuse authorization for the actual shipment and notification. Never fabricate tracking, mark all orders shipped from a general read request, or resend uncertain buyer notifications. Read the receipt after acceptance and report unconfirmed outcomes honestly.

For payments/ledger reads preserve amount/divisor/currency and distinguish sales, fees, settlements and already-recorded refunds. Do not infer authority to issue refunds or transfers. General Etsy messaging, ad control and refund initiation are not available just because an order tool exists. See [index](../../references/etsy-operation-index.md) for exact supported methods.

View saved version →

---
name: manage-etsy-shop
description: Plan or manage Etsy categories, attributes, variants, personalization, shipping/processing profiles, package measurements, returns, sections and seller settings using confirmed facts; prepare manual worksheets without MCP.
---

# Manage Etsy shop settings

Read [delivery/packaging](../../references/shipping-packaging.md) for shipping and [options/personalization](../../references/variations-personalization.md) for item choices. Read [operation recipes](../../references/etsy-operation-recipes.md) for connected actions. Offline, produce complete named settings and manual field steps without invented IDs.

## Select the resource

- Category/attributes: seller taxonomy and category properties; choose the most specific accurate supported option. Do not infer materials or assign unrelated occasions. `etsy_get_listing_properties` reads the list; single-property read may return501.
- Delivery: origin/destinations, processing versus transit, confirmed packed weight/size/units, actual service/rates. A profile name does not prove paid/free rates.
- Processing: actual ready-to-ship/made-to-order times and working calendar; readiness-state and shipping-profile unit enums differ.
- Returns: seller-approved returns/exchanges/deadline; custom goods do not automatically mean no returns.
- Variants/inventory: full sellable matrix and semantic readback; preserve unchanged combinations.
- Personalization: up to five questions and 1024 text characters in MakeBox/direct Etsy, practical instructions, complete existing set and prices preserved. Optional text supports a fixed fee; variation offerings use full item prices.
- Sections/partners: real organization/maker relationships, no SEO slogans substituted for factual attributes.

## Execute accurately

Identify shop, read resource and inspect live schema. Assign an existing shipping/return profile with `etsy_update_listing` using the exact profile ID; the connector can do this on existing listings. Changing destination prices requires the destination tool, not profile metadata update.

Before editing shared profiles, show the affected scope and reuse only authorization covering it. If the request is for one item, do not change every other listing. New profile creation and subsequent assignment are different steps. Deletion/consolidation may remove a resource or move many listings; surface that consequence. Read authoritative state after each approved action.

Use the [105-operation index](../../references/etsy-operation-index.md) when a capability is unclear; inspect schema before saying it is unavailable. Tools cover the published API, not every Etsy website feature. Keep acceptance separate from verification and do not retry uncertain writes. Return settings, affected IDs, readback, unresolved facts and next step.

View saved version →

---
name: optimize-etsy-listing
description: Audit or improve an existing Etsy listing using product facts, buyer intent and available performance evidence; preserve specifications and operational settings. Return complete copy for manual use or execute approved connected edits.
---

# Optimize an Etsy listing

## Establish baseline and scope

Use pasted/exported content offline; state its timestamp/limits. Connected, prefer `etsy_get_listing` and relevant live media/inventory/personalization/profile reads. MakeBox row IDs differ from Etsy IDs. Ask whether the requested scope is text, media, specific settings or a full audit when it cannot be inferred.

Read [quality playbook](../../references/listing-quality-playbook.md) and [brief](../../references/product-brief.md). Inventory all confirmed details before editing. Preserve dimensions, contents, compatibility, customization, care, processing/returns and license. Surface contradictions rather than rewrite them as facts.

## Diagnose and propose

1. Identify the main purchase intent and current offer consistency. Look for unclear item/count, misleading photos, weak opening or missing ordering information.
2. Use [keyword evidence](../../references/keyword-research.md), with dates and missing values retained. If reports exist, separate listing/shop metrics and discovery versus conversion hypotheses. Without data do not claim a causal diagnosis or forecast.
3. Improve the chosen fields only: clear title, natural full description, distinct relevant tags and accurate attributes. Explain each meaningful change. Preserve useful existing terms unless there is a reason to replace them.
4. Audit relevant [options](../../references/variations-personalization.md), [delivery](../../references/shipping-packaging.md) and [media](../../references/media-digital.md) when the scope warrants it; do not silently change price, stock, state, shared policy or shipping.
5. Return before/after for edited fields plus the complete revised description and copy-ready set. For a long description, reorganize without losing factual sections. Use the [handoff](../../templates/listing-handoff.md).

A complete generated SEO set targets thirteen relevant valid tags. A seller-approved narrow/native update is not forced into the internal AI exact-13 rule. No invented quality score or guaranteed Etsy result.

## Apply only the intended changes

Standalone: manual fields, preview and save instructions; no claimed write. Connected: inspect `etsy_update_listing` schema, show exact changed fields, reuse authorization for them, send once and read back. Text transport does not need MakeBox generation.

If the seller specifically requests MakeBox internal `optimize_listing` or bulk AI, disclose/quote allowance first; generated output is a proposal. For bulk use `quote_bulk_seo` → approved `start_bulk_seo` → `get_bulk_seo_job` → review → approved push. Preserve per-listing review and partial statuses. Never automatically replay an uncertain Etsy write or paid generation.

Record baseline, changes, next evaluation window and verified/unverified status. Use [release check](../../checklists/listing-release.md).

View saved version →

---
name: research-etsy-market
description: Research product-relevant Etsy keywords, competitors and niches from seller reports, CSVs, public samples or MakeBox estimates; explain sources, missing metrics and selection reasons without inventing demand or ranking guarantees.
---

# Research keywords and niches

Read [research guide](../../references/keyword-research.md). First establish item, real traits, buyer intent, language/market and scope; use [brief](../../references/product-brief.md) only for missing relevant facts.

## Workflow

1. Gather seller search/conversion reports or supplied datasets with date/definitions. MCP absent: analyze these locally or use authorized public browsing. With no numeric evidence, provide clearly labelled semantic hypotheses.
2. Build intent groups and reject misleading materials/product types, unrelated holidays and unauthorized brands before ranking candidates.
3. Connected: `search_keywords` finds candidates (up to100); `check_keywords` validates batches of at most40. `competitor_tags`/`search_top_listings` give sample language/offers. Inspect each current schema; direct public alternatives are in the [index](../../references/etsy-operation-index.md).
4. With thousands of CSV terms, filter/deduplicate and shortlist rather than making thousands of calls. Missing statistics remain unknown. Compare relevance, intent and coverage before volume/competition.
5. Compare like-for-like offers, not a single cup versus a set or a template versus print. Shop lifetime sales are not listing sales; returned search order is not universal rank.
6. Deliver the [evidence table](../../templates/keyword-evidence.md), recommended primary phrase, title/tag allocation, rejected misleading phrases and a feasible test plan. Tags fit ≤20 characters; natural longer phrases may remain in prose.

Retain supplied clicks/trends/seasonality only if actually present and defined. Provider opportunity is not a conversion probability. Never claim exact search demand from tag frequency, guarantee top placement, copy protected content or request private competitor orders. Research alone does not authorize any shop change or paid internal generation.

View saved version →

---
name: use-etsy-api
description: Discover and use MakeBox direct Etsy API tools with exact schemas, seller-owned identity, file transport, precise authorization and authoritative readback; avoid guessed endpoints and duplicate uncertain writes.
---

# Direct Etsy API

Read [transport contract](../../references/direct-etsy-api-guide.md) and [operation recipes](../../references/etsy-operation-recipes.md). Search the [105-operation index](../../references/etsy-operation-index.md) for the task, then inspect the live tool schema. The bundled [schemas](../../references/etsy-tool-schemas.json) are a dated fallback/reference, not authority to call unavailable tools.

## Operating contract

1. No MCP: do not invent a tool or demand connection for copy work. Produce manual fields/settings with the appropriate skill. Only external execution waits for connection.
2. Connected: `list_shops`/`get_account_status` establish selected MakeBox workspace/access, `etsy_get_me` Etsy identity. Private shop/user IDs are server-bound; public calls may expose shop IDs. Etsy listing IDs differ from MakeBox row IDs.
3. Read current resource; collect missing facts. Inspect required params/body/enums and media input. Do not infer an API limitation from a narrower convenience tool.
4. Prepare exact changes and show affected scope/consequence. Reuse prior explicit authorization for that same scope. Only an authorized write gets `confirm:true`; deletion also needs the current `expected_title` where required.
5. Use direct tools for chat-authored approved payloads; no internal model or AI allowance needed to transport them. Plans, scopes and Etsy fees can still apply. Optional generation/research workflows have separate costs/quotas.
6. Follow returned readback hint or matching authoritative read. Acceptance with `verified:false` is not completed state. On timeout/mismatch read first; never automatically replay.

Body fields belong inside `body`; path/query params at top level. Preserve omission, false, zero and permitted clears. Use native enum values: direct `download` is not convenience `digital`. Binary fields take tenant-owned asset references, not arbitrary server/local paths. See recipes for examples validated against the server snapshot.

Full inventory and personalization writes replace complete sets: preserve untouched values and convert GET-only structures to the writable schema. Shared profile edits can affect many listings. Public research does not authorize private competitor access.

Report target IDs, source/capture time, accepted/verified status and the real unresolved error. Never expose tokens or imply API supports every website feature, general buyer messaging, purchases, ad changes or refund initiation.

View saved version →

---
name: visual-etsy-workspace
description: Open the MakeBox listings workspace when a seller asks for a visual catalogue or wants to select a listing for discussion. Works only when the connected MCP server exposes the workspace tool and the host supports MCP Apps.
---

Call `get_account_status` at the start of the task. If the seller asks to browse visually and `open_makebox_workspace` is available, call it with no arguments. It presents MakeBox saved listings and separate live Etsy active and draft views. The SEO screen can quote a paid SEO job and start it only after the seller confirms the shown cost; its results remain in MakeBox. Creating a listing and researching keywords begin in chat. When the host does not render MCP Apps or the tool is unavailable, use the existing `list_listings` and `get_listing` tools instead; never claim the view opened when it did not.

MakeBox listing IDs and Etsy listing IDs are separate namespaces. For a saved MakeBox item use its MakeBox ID with `get_listing` and `live:false`; for an Etsy item use its Etsy ID with `etsy_get_listing`. Verify the returned item before any operation. Distinguish Etsy live data from the MakeBox mirror. Never invent photos, SKU, price currency or other missing fields. Opening and browsing the workspace are read-only. Existing seller approval and verification requirements still apply to every change, paid generation and Etsy publication.