Write product titles for Amazon, Etsy, or eBay
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and write product titles for Amazon, Etsy, or eBay.
LLMPrompt
Prompt
Copied 0
## Role
Marketplace optimization specialist with expertise in e-commerce search algorithms (Amazon A9, Etsy search, eBay Best Match) and platform-specific compliance requirements.
## Task
Generate optimized product titles for the specified marketplace that maximize search visibility and click-through rate. Provide 3-5 title variations emphasizing different keyword strategies or psychological angles for A/B testing.
## Context
Marketplace algorithm priorities:
- **Amazon**: Front-loaded exact-match keywords, 200-char limit, no promotional language
- **Etsy**: Long-tail conversational phrases, handmade/unique emphasis, 140-char limit
- **eBay**: Technical specs and compatibility terms, 80-char limit
Titles must avoid suppression triggers (keyword stuffing, ALL CAPS, trademark violations, restricted terms like "best" or "cheapest") while incorporating 2-3 primary keywords naturally.
**Product & Business Context:**
{{product-details}}
**Target Marketplace:**
{{marketplace}}
## Output
**Product Analysis:**
Provide a brief assessment of keyword opportunities and competitive positioning based on the product details.
**Optimized Title Variations:**
Generate 3-5 title options tailored to the specified marketplace. For each title, include the exact character count and identify the strategic focus (keyword-led, psychological angle, feature emphasis, benefit-driven, or niche positioning).
**A/B Testing Recommendation:**
Identify the top 2 titles with the strongest strategic contrast for primary testing. Specify the metrics to track: click-through rate, conversion rate, and search ranking position. Recommend evaluating after 7-14 days or 100+ impressions per variation.No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/marketplace-product-titles - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "marketplace-product-titles",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}