- Brand
- EverBee
- Category
- Data & Analytics
- Primary Subcategory
- Market & Competitive Intelligence Data
Integration details
Description
EverBee tracks millions of Etsy listings, shops and keywords and estimates their sales, revenue and search demand. EverBee Research brings that data into ChatGPT. Ask in plain language, and answers come back as interactive tables and cards. What you can ask: - "Find bestselling personalized jewelry listings under $40 with at least 100 sales a month." - "Give me a teardown of my top competitor's shop." - "Is 'custom pet portrait' a good product to sell? Check demand and competition." - "Find niches inside wedding decor with low competition." - "What tags do the top 20 boho wall art listings share?" - "Estimate my profit on a $35 mug after Etsy fees and shipping." What's inside: - Listing analytics: estimated monthly sales and revenue, total sales, reviews, conversion rate, tags, listing age. - Shop analytics: 30-day sales and revenue, review rate, price distribution, buyer reviews. - Keyword research: Etsy search volume, competition, trend, related keywords. - Analysis: product-idea verdict with a 0-100 opportunity score, niche discovery, tag patterns, profit estimates. - Your EverBee account: favorite folders, saved filters, and a dashboard for your connected Etsy shops. Limitations: covers Etsy only. Sales and revenue are EverBee estimates, not Etsy-reported figures. Access: sign in with your EverBee account.
- Integration type
- Plugin
- Verification status
- Not applicable
- Platform
- ChatGPT
- Primary Subcategory
- Market & Competitive Intelligence Data
- Secondary Subcategories
- None listed
- Brand
- EverBee
- Access
- Account required
- First tracked
- 2026-11-14
- Tool count
- 45
- Market
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Not discoverable in ChatGPT yet
ChatGPT now suggests Plugins on its own when they match a user's request, but not every Plugin is being surfaced yet.We haven’t seen EverBee Research suggested yet. Sign up and we’ll track it, and your Discoverability Score will appear here once ChatGPT starts surfacing it.
What discovery looks like

Get alerts for EverBee Research
Get updates when EverBee Research’s Discoverability Score or category rank changes.
Competing in ChatGPT Market & Competitive Intelligence Data
View Category45 tools agents can invoke
Add listings, shops, or keywords to a favorite folder. `folder_id` comes from create_favorite_folder or list_favorite_folders. `items` are the PUBLIC handles matching the folder's kind: - listing folder -> listing_id values (e.g. "1234567890") - shop folder -> shop_name values (e.g. "MyShopName") - keyword folder -> the keyword text (e.g. "custom dog collar") (These are the same handles returned by get_listings / get_shops / get_keywords.) Adding an item already in the folder is a no-op. Returns `{folder: {...}, added: [...], already_present: [...], not_found: [...]}` echoing the handles back. `not_found` = handles that didn't match anything. If the user's plan favorite limit would be exceeded (shops/keywords), returns a 403-style error with `suggested_upgrade` and no items are added.
add_items_to_folder
Finds the best-selling listings for a keyword or niche on Etsy. Use when a seller wants to see top sellers, what's making money, or the highest-performing products in a space. Returns listings ranked by revenue (or another metric) with sales, price, and shop, plus a summary of the pattern among winners.
find_bestsellers
Create a favorite folder to organize favorites of one kind. `type` is 'listing', 'shop', or 'keyword' — a folder holds only that kind. `name` is whatever the user calls it, e.g. 'red tshirt'. Idempotent: if a folder with this name already exists for this type it is returned as-is (never duplicated) — safe to call before adding items. Returns `{folder: {id, name, type, ...}, created: true|false}` (`created:false` means an existing folder was reused). Then pass `folder.id` to add_items_to_folder. If the user's plan folder limit is reached, returns a 403-style error with a `suggested_upgrade`.
create_favorite_folder
Save a set of filter conditions as a named custom filter — the EverBee app's "+ New Filter" pills on Product Analytics (`module="listings"`) and Shop Analyzer (`module="shops"`). Business plan only. Use when the user says "save these filters", "save this as <name>". It appears in the web app too. Apply it later with `saved_filter_id` on view_listings / view_shops. Returns `{filter: {id, name, module, filters, updated_at}, created: true, ignored: [...]}`. Errors: `business_plan_required` (with `suggested_upgrade`), `name_taken`, `invalid_filters` (lists the allowed keys).
create_saved_filter
Delete a favorite folder and everything saved in it. `folder_id` comes from create_favorite_folder or list_favorite_folders. Destructive — confirm with the user first. Returns `{message: "..."}`.
delete_favorite_folder
Delete a saved filter (here and in the EverBee web app). `filter_id` comes from view_saved_filters. Destructive — confirm with the user first. Returns `{message: "..."}`.
delete_saved_filter
Explains what EverBee's research metrics mean. Use when a seller asks what a metric means, or when the agent needs to correctly interpret a score before explaining a result. Returns plain-language definitions. Pass `metric` (e.g. "Visibility Score") for one, or omit it for all.
explain_metrics
Show ONE favorite folder's saved items as a rich table. PREFER THIS over the raw get_favorite_folder tool when the user wants to see what's in a folder. `folder_id` comes from list_favorite_folders / create_favorite_folder. Shows 20 items per page with Previous / Next buttons. The columns adapt to the folder's kind, so which fields exist depends on it. DEFAULT: omit `columns` — the table then shows that kind's default set, the same columns the EverBee app shows. Pass it ONLY when the user names the fields they want; it REPLACES the default set rather than extending it, so a partial list hides every column you leave out. When you do pass it, an entry may be the EverBee app label the user says or the backend field key — for a listing folder "Sales" and "est_mo_sales" both resolve.
view_favorite_folder
Another page of a widget table, for its Previous / Next buttons. Not for the model.
fetch_table_page
Returns the valid Etsy category taxonomy. Use to scope a search to a valid category or to list available categories. Returns category names and identifiers — the identifier is what `category_include` takes on view_listings / view_shops / saved filters.
get_categories
Get a favorite folder's details and the items saved in it (paginated). Raw JSON — for programmatic use. Prefer **view_favorite_folder** whenever the result will be shown to the user; use THIS tool only when you need the data to compute something yourself. `folder_id` comes from create_favorite_folder or list_favorite_folders. The item kind is derived from the folder, so results are all listings, all shops, or all keywords with their full analytics. Returns `{folder: {id, name, type, items_count, ...}, current_page, total_count, total_pages, results: [...]}` — `results` holds the same rich analytics payloads as get_listings / get_shops / get_keywords.
get_favorite_folder
Get keyword suggestions and analytics related to a seed keyword. Raw JSON — for programmatic use. Prefer **view_keyword** whenever the result will be shown to the user; use THIS tool only when you need the data to compute something yourself. Use when the user gives a seed term — "keywords like <word>", "what should I tag a <thing> listing with". The same filters/sort/pagination as get_keywords narrow the suggestions. Returns: {current_page, total_count, total_pages, searched_keyword: [...], results: [{keyword, vol, cpc, competition, new_volume, score}, ...]}. `searched_keyword` is the seed term's OWN analytics and is never capped or masked on any plan; `results` are the suggestions. `new_volume` is the field the EverBee app shows as "Volume"; `vol` is a legacy duplicate of it. Plan limits: on Hobby and Pro `results` is capped at the first 10 suggestions (the seed term itself is dropped from them, since it is already in `searched_keyword`) and `plan_limit` = {limit, max_page, total_matching, message} is added. When it is present, `total_count`/`total_pages` describe what was returned and `plan_limit.total_matching` is the real match count. Nothing is masked — there are just fewer rows. On those plans `order_by`, `keyword_include`/`keyword_exclude`, any `*_min`/`*_max` range, and any `page` above 1 all return a 403 with an explanatory `error`. Do NOT retry — relay the message.
get_keyword
Browse Etsy keyword analytics — search volume, competition, and score. Raw JSON — for programmatic use. Prefer **view_keywords** whenever the result will be shown to the user; use THIS tool only when you need the data to compute something yourself. When to use: keyword research not tied to a seed word — "high-volume, low-competition keywords", "trending keywords with score over X". For suggestions related to a specific term, use get_keyword(keyword). Filters: keyword_include/exclude (partial match) and min/max ranges for new_volume, competition, score. Sort with order_by + order_direction — see the `order_by` field description for the accepted metrics and the EverBee app label each one maps to. Returns: {current_page, total_count, total_pages, results: [{keyword, vol, cpc, competition, new_volume, score}, ...]}. `new_volume` is the field the EverBee app shows as "Volume"; `vol` is a legacy duplicate of it. Plan limits: on Hobby and Pro the API returns only the first 10 keywords per search, and adds `plan_limit` = {limit, max_page, total_matching, message}. When it is present, `total_count`/`total_pages` describe what was returned and `plan_limit.total_matching` is the real number of matching keywords. Every value in every row is genuine — nothing is masked, there are just fewer rows. On those plans `order_by`, `keyword_include`/`keyword_exclude`, any `*_min`/`*_max` range, and any `page` above 1 all return a 403 with an explanatory `error`. Do NOT retry or work around it — relay the message and, if the user needs more, fetch the uncapped default-ordered page 1.
get_keywords
Fetch full analytics for a single Etsy listing by its listing_id. Raw JSON — for programmatic use. Prefer **view_listing** whenever the result will be shown to the user; use THIS tool only when you need the data to compute something yourself. Use after get_listings to drill into one result, or when the user gives a specific listing id. `currency` is an optional ISO code (e.g. USD) for the monetary fields. `time_range` sets the window for the estimated metrics AND for the `trends` series: last_30_days, last_1_month (the default), last_3_months, last_6_months, last_12_months, last_24_months, all_time. Pass it when the user asks how a listing has done over a period — est_mo_sales, est_mo_revenue and growth_rate are that window's TOTALS (a 24-month range gives a 24-month total, not a monthly average), and `trends` is bucketed daily for the first three, monthly for the rest. Any other value silently returns an empty series. Because est_mo_sales is that window's total, `cached_est_mo_sales` and `cached_est_mo_revenue` are also returned and are ALWAYS last month's figures, whatever `time_range` says — they are what the EverBee app and browser extension show as "Mo. Sales"/"Mo. Revenue". Quote those when the user asks what a listing sells per month, and never multiply est_mo_sales by 12 without checking the window first. `est_total_sales` is estimated lifetime sales. Returns: {listing: {...}} with title, price, shop, estimated sales/revenue/ reviews, views, favorers, tags, trends, taxonomy_path, and Shop details.
get_listing
Raw JSON listing analytics — for programmatic use, NOT for showing a user. Prefer **view_listings** for anything a person will see ("find top-selling X", "best listings for <thing>", "what's already selling in <niche>", competitive research): it renders the same data as a rich sortable table with a KPI summary. Use THIS tool only when you need the raw records to compute/aggregate/ filter further yourself, or to feed another tool — not to present results. Filtering: range filters come in `*_min`/`*_max` pairs (e.g. est_mo_revenue_min); text filters are partial-match `*_include`/`*_exclude`. Sort with order_by + order_direction — see the `order_by` field description for the metrics a seller researches by and the EverBee app label each one maps to. Paginate with page + per_page. Returns: {current_page, total_count, total_pages, results: [listing, ...]}. Each listing carries title, price, shop_name, est_mo_sales, est_mo_revenue, est_reviews, views, num_favorers, conversion_rate, tags, url, and more. Use get_listing(listing_id) for one listing's full detail. SALES FIELDS — three metrics, three different questions: - `est_mo_sales` is the SELECTED `time_range`'s TOTAL, not a monthly rate. time_range="all_time" puts LIFETIME sales in it; "last_24_months" puts a 24-month total in it. Only at the default last_1_month is it a monthly figure. - `cached_est_mo_sales` is always LAST MONTH, whatever `time_range` says. This is the number the EverBee app and browser extension label "Mo. Sales", so it is the one to quote when a user asks "how many does this sell per month?". - `est_total_sales` is estimated LIFETIME sales. `est_mo_revenue`/`cached_est_mo_revenue` split the same way. Never multiply `est_mo_sales` by 12 to get an annual figure without checking `time_range` first.
get_listings
Fetch full analytics for a single Etsy shop by exact shop_name. Use after get_shops to drill into one shop, or when the user names a shop. For the shop's listings, call get_shop_listings(shop_name). Returns a shop object: shop_name, sales_30_days, revenue_30_days, revenue, review_count, review_average, conversion_rate, listings_count, listing_active_count, num_favorers, shop_age_month, on_etsy_since, average_listing_price, shop_location_country_iso, and more.
get_shop
List all analyzed listings for one Etsy shop, with the same filters as get_listings. Raw JSON — for programmatic use. Prefer **view_shop_listings** whenever the result will be shown to the user; use THIS tool only when you need the data to compute something yourself. Use when the user names a shop and wants its catalog — "show me <shop>'s best-sellers", "what does <shop> sell under $20". `shop_name` is the exact shop identifier. Filters/sort/pagination match get_listings. Returns: {current_page, total_count, total_pages, results: [listing, ...]}. Sales fields carry the same three meanings as in get_listings: `est_mo_sales` is the selected `time_range`'s TOTAL, `cached_est_mo_sales` is always last month (the app's "Mo. Sales"), `est_total_sales` is lifetime.
get_shop_listings
Raw JSON shop analytics — for programmatic use, NOT for showing a user. Prefer **view_shops** for anything a person will see ("top shops selling X", "biggest sellers in <niche>", competitor discovery): it renders the same data as a rich sortable table with a KPI summary. Use THIS tool only when you need the raw records to compute/aggregate/filter further yourself, or to feed another tool — not to present results. Filters: text match on shop_name (exact) / shop_name_include (partial) / category / currency_code / shop_location_country_iso, plus a `<field>_min` / `<field>_max` pair for every shop metric — Total Sales (transaction_sold_count), Total Revenue (revenue), Shop Age (shop_age_month), Reviews, Total Favorites, Active Listings and the rest. Sort with order_by + order_direction — see the `order_by` field description for the accepted metrics and the EverBee app label each one maps to. Returns: {current_page, total_count, total_pages, results: [shop, ...]} with shop_name, sales_30_days, revenue_30_days, review_count, conversion_rate, listings_count, shop_age_month, and more. Use get_shop(shop_name) for detail and get_shop_listings(shop_name) for its catalog. Three returned fields are DERIVED per row rather than indexed, so they cannot be sorted or filtered by: listings_count, average_calculated_revenue, on_etsy_since. Bound listing_active_count, revenue and shop_age_month instead.
get_shops
Show keyword SUGGESTIONS for one seed term as a rich table. PREFER THIS when the user gives a seed word — 'keywords like <word>', 'what should I tag a <thing> listing with'. `keyword` is the seed term; the table lists related keywords with their analytics. DEFAULT: omit `columns`. The widget then shows the same default columns the EverBee app shows, which is what the user expects to see — and the set is wide, so leaving it alone is almost always right. Pass `columns` ONLY when the user names the keyword fields they want, or asks to add or drop one ("show me price and views", "just the keyword and its volume", "add conversion rate"). It REPLACES the default set — it does not extend it — so a partial list hides every column you leave out. Filtering or sorting on a field is NOT such a request: those fields are appended automatically, and the rest of the default set still shows. When you do pass it, list the fields in display order. Each entry may be the EverBee app label the user says OR the backend field key — "Volume" and "new_volume" both resolve, and matching ignores case, punctuation and spacing. Unresolvable names are dropped silently. Available — label (field key): "Keyword" (keyword), "Volume" (new_volume), "Competition" (competition), "Keyword Score" (score), "Volume (legacy)" (vol), "CPC" (cpc). Default set (what you get by omitting `columns`): "Keyword", "Volume", "Competition", "Keyword Score". Rows: the table always shows 20 per page with Previous / Next. When the user asks for an exact number ("51 listings", "top 5"), set `limit` to it; otherwise leave `limit` and `params.per_page` unset to page through every match.
view_keyword
Show Etsy keyword analytics to a person as a rich table. PREFER THIS for user-facing keyword research — 'best keywords for <niche>', 'high-volume low-competition terms', SEO/tag planning, and any filtered or sorted keyword request. Use it by default for such requests; only fall back to the raw get_keywords tool when you need the JSON to compute something yourself. DEFAULT: omit `columns`. The widget then shows the same default columns the EverBee app shows, which is what the user expects to see — and the set is wide, so leaving it alone is almost always right. Pass `columns` ONLY when the user names the keyword fields they want, or asks to add or drop one ("show me price and views", "just the keyword and its volume", "add conversion rate"). It REPLACES the default set — it does not extend it — so a partial list hides every column you leave out. Filtering or sorting on a field is NOT such a request: those fields are appended automatically, and the rest of the default set still shows. When you do pass it, list the fields in display order. Each entry may be the EverBee app label the user says OR the backend field key — "Volume" and "new_volume" both resolve, and matching ignores case, punctuation and spacing. Unresolvable names are dropped silently. Available — label (field key): "Keyword" (keyword), "Volume" (new_volume), "Competition" (competition), "Keyword Score" (score), "Volume (legacy)" (vol), "CPC" (cpc). Default set (what you get by omitting `columns`): "Keyword", "Volume", "Competition", "Keyword Score". Rows: the table always shows 20 per page with Previous / Next. When the user asks for an exact number ("51 listings", "top 5"), set `limit` to it; otherwise leave `limit` and `params.per_page` unset to page through every match.
view_keywords
List the user's favorite folders for one kind of item. `type` is 'listing', 'shop', or 'keyword'. Use this to find a folder (by its `name`) before adding items, or to show the user their folders. Returns `{type, folders: [{id, name, type, is_default, items_count, last_used_at, created_at}], plan: {folder_limit, folder_count, can_create_folder, favorite_limit, favorite_count, suggested_upgrade}}`. Pass a folder's `id` to get_favorite_folder / add_items_to_folder.
list_favorite_folders
Show ONE Etsy listing's full analytics to a person as a branded detail card — headline KPIs (price, estimated monthly revenue/sales, conversion) plus every populated field. PREFER THIS over the raw get_listing tool when the user drills into a single listing. `currency` is an optional ISO code (e.g. USD) for the monetary fields.
view_listing
Show ONE listing's tags with their keyword analytics — volume, competition, keyword score — as a rich table, the same panel the EverBee app shows under a listing. Use it when the user asks about a listing's tags, its SEO, or which of its keywords are worth targeting. For tags across SEVERAL listings — a shop's best sellers, a niche's top listings, keywords to replicate — use view_tag_patterns instead: one table, never one view_listing_tags call per listing. COST: the listing's tags carry no analytics of their own, so this makes one extra keywords request per tag (up to 13). Call it only when the user actually asks about tags — view_listing already shows the tag text itself.
view_listing_tags
One listing's trend series for one preset window, formatted for the trends modal. Called by the listings widget, not by the model.
listing_trend_detail
Show Etsy listing analytics to a person as a rich table. PREFER THIS for any user-facing product research — 'find top-selling <thing>', 'best listings for <niche>', 'what's already selling', competitive research, and any filtered or sorted request ('listings with between 100 and 200 total sales', 'digital products over $50 sorted by revenue'). Use it by default for such requests; only fall back to the raw get_listings tool when you need the JSON to compute something yourself. DEFAULT: omit `columns`. The widget then shows the same default columns the EverBee app shows, which is what the user expects to see — and the set is wide, so leaving it alone is almost always right. Pass `columns` ONLY when the user names the listing fields they want, or asks to add or drop one ("show me price and views", "just the keyword and its volume", "add conversion rate"). It REPLACES the default set — it does not extend it — so a partial list hides every column you leave out. Filtering or sorting on a field is NOT such a request: those fields are appended automatically, and the rest of the default set still shows. When you do pass it, list the fields in display order. Each entry may be the EverBee app label the user says OR the backend field key — "Product" and "title" both resolve, and matching ignores case, punctuation and spacing. Unresolvable names are dropped silently. Available — label (field key): "Product" (title), "Shop Name" (shop_name), "Price" (price), "Sales" (est_mo_sales), "Revenue" (est_mo_revenue), "Mo. Sales" (cached_est_mo_sales), "Mo. Revenue" (cached_est_mo_revenue), "Trends" (trends), "Growth Rate" (growth_rate), "Total Sales" (est_total_sales), "Total Reviews" (est_reviews), "Listing Age" (listing_age_in_months), "Total Favorites" (num_favorers), "Avg. Reviews" (est_reviews_in_months), "Total Views" (views), "Category" (main_category), "# of Tags used" (tags_used), "Auto Renews" (should_auto_renew), "Is Customizable" (is_customizable), "Is Personalizable" (is_personalizable), "Has Variations" (has_variations), "Is Supply" (is_supply), "Minimum Processing" (processing_min), "Placement of Listing in Shop" (featured_rank), "Shipped From" (shipping_from_country_iso), "Shop Age" (shop_age_month), "Visibility Score" (visibility_score), "Conversion Rate" (conversion_rate), "Review ratio" (shop_review_ratio), "Shop Digital Listings" (digital_listing_count), "Title Character Count" (title_character_count), "When Made" (when_made), "Who Made" (who_made), "Total Shop Sales" (transaction_sold_count), "Listing Type" (listing_type), "Tags" (tags), "URL" (url). Default set (what you get by omitting `columns`): "Product", "Shop Name", "Price", "Sales", "Revenue", "Trends", "Growth Rate", "Total Sales", "Total Reviews", "Listing Age", "Total Favorites", "Avg. Reviews", "Total Views", "Category", "Shop Age", "Visibility Score", "Conversion Rate", "Total Shop Sales", "Listing Type". Rows: the table always shows 20 per page with Previous / Next. When the user asks for an exact number ("51 listings", "top 5"), set `limit` to it; otherwise leave `limit` and `params.per_page` unset to page through every match. Use ListingsParams filters/order_by to narrow and sort the underlying query.
view_listings
Show the user's OWN shop performance — the EverBee app's My Shop dashboard — across ALL of their connected Etsy shops: gross revenue, orders, average order value, LTV, unique buyers and repeat-customer rate for `time_range`, a revenue chart, a per-shop breakdown and their top-selling listings. Use for 'how is my shop doing', 'my sales this month', 'compare my shops'. Pass `shop_names` only to focus on some of the user's shops. Amounts are in the user's default currency. Their catalog: view_shop_listings(shop_name).
view_my_shop
Show the user's EverBee account: plan, default currency, connected shops, research lookups used this month and favorites limits. Use for 'what plan am I on', 'my account', 'how many favorites can I save'. Billing, password and subscription changes happen in the EverBee web app — the response links there.
view_my_account
Discovers product niches and opportunities within a broad interest or category. Use this when a seller wants to find something to sell, is exploring a space, or asks for low-competition or high-opportunity niches. Returns sub-niches ranked by opportunity score with the demand, competition, and pricing behind each, plus a summary naming the standouts.
discover_niches
Health check tool to verify the MCP server is running.
ping
Validates whether a specific product idea is worth selling on Etsy. Use this whenever a seller asks if a product would sell, whether they should start selling something, or wants a go/no-go on a product idea. Returns a verdict (strong opportunity / proceed with caution / oversaturated / too niche), an opportunity score, and the demand, competition, revenue, saturation, and seasonality signals behind it, plus a plain-language summary.
validate_product_idea
Estimates profit and margin for an Etsy sale after fees and costs. Use when a seller asks about profit, margin, or whether a price is profitable after Etsy's fees. Returns net profit, margin %, and a fee breakdown, plus a summary flagging thin margins.
estimate_profit
Remove listings, shops, or keywords from a favorite folder. `folder_id` comes from create_favorite_folder or list_favorite_folders. `items` are the PUBLIC handles matching the folder's kind (listing_id, shop_name, or keyword text) — same handles used by add_items_to_folder. Removing an item that isn't in the folder is a no-op. Returns `{folder: {...}, removed: [...], not_present: [...], not_found: [...]}` echoing the handles back. This only removes items from this folder; it does not delete the folder.
remove_items_from_folder
Rename a favorite folder. `folder_id` comes from create_favorite_folder or list_favorite_folders; `name` is the new name. Returns `{folder: {id, name, type, ...}}`, or an error (e.g. if another folder of the same type already uses that name).
rename_favorite_folder
Show every Etsy shop the user has connected to EverBee (their sales channels): name, title, total sales, monthly revenue, active listings, rating and connection status. Use for 'which shops are connected', 'my shops', 'my sales channels'. Connecting or disconnecting a shop happens in the EverBee web app — the response carries that link.
view_sales_channels
Show the user's saved (custom) filters for Product Analytics (`module="listings"`) or Shop Analyzer (`module="shops"`) — the "+ New Filter" pills in the EverBee app. Business plan only. Use when the user asks what filters they've saved, or before applying, renaming or deleting one: each row's `filter_id` goes to view_listings / view_shops (`saved_filter_id`), update_saved_filter or delete_saved_filter.
view_saved_filters
Set the user's EverBee display currency (ISO code, e.g. "EUR") — the currency selector in the EverBee app. Every later result here and in the web app shows amounts in it. Use for "show prices in euros from now on". For one search only, pass `currency` to that view instead. Returns `{default_currency}`.
set_default_currency
Show ONE Etsy shop's full analytics to a person as a branded detail card — headline KPIs (sales, revenue, conversion, reviews) plus every populated field. PREFER THIS over the raw get_shop tool when the user names a single shop and wants to see it. `shop_name` must be the exact shop identifier. For that shop's catalog use view_shop_listings instead. `currency` is an optional ISO code (e.g. USD) the monetary fields are converted into.
view_shop
Show ONE shop's listings to a person as a rich table — the same layout as view_listings, scoped to `shop_name`. PREFER THIS when the user names a shop and wants its catalog: '<shop>'s best sellers', 'what does <shop> sell under $20'. `shop_name` must be the exact shop identifier. DEFAULT: omit `columns`. The widget then shows the same default columns the EverBee app shows, which is what the user expects to see — and the set is wide, so leaving it alone is almost always right. Pass `columns` ONLY when the user names the listing fields they want, or asks to add or drop one ("show me price and views", "just the keyword and its volume", "add conversion rate"). It REPLACES the default set — it does not extend it — so a partial list hides every column you leave out. Filtering or sorting on a field is NOT such a request: those fields are appended automatically, and the rest of the default set still shows. When you do pass it, list the fields in display order. Each entry may be the EverBee app label the user says OR the backend field key — "Product" and "title" both resolve, and matching ignores case, punctuation and spacing. Unresolvable names are dropped silently. Available — label (field key): "Product" (title), "Shop Name" (shop_name), "Price" (price), "Sales" (est_mo_sales), "Revenue" (est_mo_revenue), "Mo. Sales" (cached_est_mo_sales), "Mo. Revenue" (cached_est_mo_revenue), "Trends" (trends), "Growth Rate" (growth_rate), "Total Sales" (est_total_sales), "Total Reviews" (est_reviews), "Listing Age" (listing_age_in_months), "Total Favorites" (num_favorers), "Avg. Reviews" (est_reviews_in_months), "Total Views" (views), "Category" (main_category), "# of Tags used" (tags_used), "Auto Renews" (should_auto_renew), "Is Customizable" (is_customizable), "Is Personalizable" (is_personalizable), "Has Variations" (has_variations), "Is Supply" (is_supply), "Minimum Processing" (processing_min), "Placement of Listing in Shop" (featured_rank), "Shipped From" (shipping_from_country_iso), "Shop Age" (shop_age_month), "Visibility Score" (visibility_score), "Conversion Rate" (conversion_rate), "Review ratio" (shop_review_ratio), "Shop Digital Listings" (digital_listing_count), "Title Character Count" (title_character_count), "When Made" (when_made), "Who Made" (who_made), "Total Shop Sales" (transaction_sold_count), "Listing Type" (listing_type), "Tags" (tags), "URL" (url). Default set (what you get by omitting `columns`): "Product", "Price", "Sales", "Revenue", "Trends", "Growth Rate", "Total Sales", "Total Reviews", "Listing Age", "Total Favorites", "Avg. Reviews", "Total Views", "Category", "Visibility Score". Rows: the table always shows 20 per page with Previous / Next. When the user asks for an exact number ("51 listings", "top 5"), set `limit` to it; otherwise leave `limit` and `params.per_page` unset to page through every match.
view_shop_listings
Show an Etsy shop's buyer reviews — newest first by default, or `sort_by="rating"` with `sort_order="asc"` for the worst first — plus its rating breakdown. Use for 'what do buyers say about <shop>', 'complaints', 'review analysis'. Works for the user's own shops and competitors.
view_shop_reviews
Produces a competitor teardown for an Etsy shop. Use when a seller names a shop and wants to understand it, asks why a competitor is succeeding, or wants to break down what another shop sells. Returns revenue drivers, pricing strategy, tag patterns, and launch cadence, plus a summary of why the shop is winning and where the gaps are. `shop_name` is the exact shop name.
analyze_shop
Show Etsy shop analytics to a person as a rich table. PREFER THIS for any user-facing shop research — 'top/best/biggest shops', 'who's selling <thing>', 'shops doing over $X/mo', competitor discovery, and any filtered or sorted request ('shops with over 1,000 sales sorted by revenue'). Use it by default for such requests; only fall back to the raw get_shops tool when you need the JSON to compute something yourself. DEFAULT: omit `columns`. The widget then shows the same default columns the EverBee app shows, which is what the user expects to see — and the set is wide, so leaving it alone is almost always right. Pass `columns` ONLY when the user names the shop fields they want, or asks to add or drop one ("show me price and views", "just the keyword and its volume", "add conversion rate"). It REPLACES the default set — it does not extend it — so a partial list hides every column you leave out. Filtering or sorting on a field is NOT such a request: those fields are appended automatically, and the rest of the default set still shows. When you do pass it, list the fields in display order. Each entry may be the EverBee app label the user says OR the backend field key — "Total Sales" and "transaction_sold_count" both resolve, and matching ignores case, punctuation and spacing. Unresolvable names are dropped silently. Available — label (field key): "Shop Name" (shop_name), "Total Sales" (transaction_sold_count), "Total Revenue" (revenue), "Mo. Sales" (sales_30_days), "Mo. Revenue" (revenue_30_days), "Shop Age" (shop_age_month), "Shop Review Score" (review_average), "Reviews" (review_count), "Total Favorites" (num_favorers), "Category" (category), "Currency" (currency_code), "Location" (shop_location_country_iso), "Active Listings" (listing_active_count), "Digital Listings" (digital_listing_count), "Review Rate" (review_rate), "Conversion Rate" (conversion_rate), "Total Views" (views), "Average price" (average_listing_price), "Listings" (listings_count), "Est. Total Revenue" (average_calculated_revenue), "Sales per Listing" (sale_per_listing), "On Etsy since" (on_etsy_since). Default set (what you get by omitting `columns`): "Shop Name", "Total Sales", "Total Revenue", "Mo. Sales", "Mo. Revenue", "Shop Age", "Shop Review Score", "Reviews", "Total Favorites", "Category", "Currency", "Location", "Active Listings", "Digital Listings". Rows: the table always shows 20 per page with Previous / Next. When the user asks for an exact number ("51 listings", "top 5"), set `limit` to it; otherwise leave `limit` and `params.per_page` unset to page through every match. Use ShopsParams filters/order_by to narrow and sort the underlying query.
view_shops
Analyzes and recommends Etsy listing tags. Use when a seller asks what tags to use, why a listing isn't ranking, or which tags top sellers use that they're missing. Returns recommended tags ranked by competitor usage and search demand, the gaps versus top competitors, plus a summary. Pass `query` (keyword or niche) or `listing_id` (compares that listing's tags with its top competitors).
analyze_tags
Show which tags (keywords) a set of top listings share, as ONE table: each tag, how many of the listings use it, those listings' total sales, and the tag's keyword volume, competition and score. PREFER THIS for 'what tags/keywords does <shop> use', 'patterns in <shop>'s best sellers', 'which tags do top <niche> listings share', 'keywords to replicate' — never call view_listing_tags once per listing for these. Pass `shop_name` (exact shop identifier) for one shop's catalog, or omit it and filter with `params` for a niche. `params` defines the set the way it does for view_listings: order_by + per_page pick the 'top N' (e.g. order_by=est_total_sales, order_direction=desc, per_page=20). COST: one listings request plus one keywords request for each of the 15 most-shared tags.
view_tag_patterns
Show upcoming holidays in the countries the user's shops sell from — the EverBee My Shop holiday calendar. Use for seasonal planning: 'what holidays are coming', 'when should I prep for Christmas / Valentine's'.
view_upcoming_holidays
Rename a saved filter and/or replace its conditions. `filters` REPLACES the saved conditions wholesale — to tweak one condition, send the full set with the change. `filter_id` comes from view_saved_filters. Returns `{filter: {...}, ignored: [...]}`.
update_saved_filter
EverBee Research ChatGPT Plugin FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve EverBee Research's ChatGPT Plugin discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are EverBee Research alternatives on ChatGPT?
As of 2026-11-15, EverBee Research competes with 10Signals, ABRAMS Trade Intelligence, AD Vantage, Adzviser Search Ads 360, AFDB, AImport.AR, AIsa GTM, akta.pro and 107 more in ChatGPT Market & Competitive Intelligence Data, ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.


