get_mcp_usage
ChatGPTReport the caller's remaining JoomPulse MCP request quota: limit, used and remaining calls per bucket (the plan total, plus MercadoLivre and Shopee where the plan meters them), with the next reset time. Calling it does not consume quota and works even when the limit is exhausted.
joompro_find_matching_products
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Find JoomPro products to source for given MercadoLivre products: up to 20 MercadoLivre ids or links in any form; an item is read as its product. A call costs one unit however many references it takes. Each JoomPro product keeps only its single best MercadoLivre match, so this lookup is incomplete: a product with no row is not found this way, which does not mean it cannot be sourced. matchScore is image and title similarity, not a probability. Of matches scoring 0.90 and above, about one in three is the same product; of matches at 0.85, about one in five. Quote it beside any profit or margin, and ask the user to confirm the pairing. joomproPrice is the lowest price across JoomPro's quantity tiers, not the price of a first order at minOrderQty.
joompro_get_category_stats
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Count and summarize the JoomPro sourcing catalogue by category or overall: products, products with a MercadoLivre match, mean JoomPro price and the median margin against the match. Group by the JoomPro category tree (English names) or by the matched MercadoLivre category (taxonomy=meli, Portuguese names), within one category if given, over the products that match where, which takes joompro_search_products' columns (no query). Groups come 100 per page: offset 100, 200, up to 900 reads the next ones. Margins are a best case at the lowest JoomPro price tier, against one automatic match per product: state the matchScore floor they were computed under.
joompro_search_products
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Search the JoomPro sourcing catalogue: products a seller in Brazil can import through JoomPro, with their landed cost, order minimums and their single best MercadoLivre match (price, profit, margin). It returns one row per JoomPro product with only that best match and cannot list every match of a product: an answer asked for all matches says so. Find products by English words in query (titles are English: translate the user's words), by category in any language, or by where on landed cost, MercadoLivre demand, price, profit, margin, match, order minimum and box; or look up one product by a joom.pro link or id in product. For given MercadoLivre products, use joompro_find_matching_products instead. Sorted by JoomPro's quality score by default: call the results top picks, never bestsellers. matchScore is image and title similarity, not a probability. Of matches scoring 0.90 and above, about one in three is the same product; of matches at 0.85, about one in five. Quote it beside any profit or margin, and ask the user to confirm the pairing. A sort by margin or profit, highest first, puts the worst matches first. joomproPrice is the lowest price across JoomPro's quantity tiers, not the price of a first order at minOrderQty.
joompro_summarize_products
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Lists, limit and the rows of one call have caps set on the server. A call asking for more is refused at no cost and the refusal says what fits, so pass what the task needs and split by it. Count and summarize the JoomPro sourcing catalogue by category or overall: products, products with a MercadoLivre match, mean and lowest JoomPro price and the median margin against the match, which does not answer a Shopee question. Group by the JoomPro category tree (English names) or by the matched MercadoLivre category (taxonomy=meli, Portuguese names), within the given categories, over the products that match where, which takes joompro_search_products' columns (no query). Groups past a cap set on the server are left out: narrow the categories or group by a higher level for the rest. Margins are a best case at the lowest JoomPro price tier, against one automatic match per product: state the matchScore floor they were computed under.
list_resources
ChatGPTList the available JoomPulse documentation resources and URI templates — each entry gives a pulse:// URI, a short label, and a one-line summary. Use the returned URIs with read_resource.
meli_get_categories
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. MercadoLivre category statistics for one month or week: revenue, orders and their change from the previous period, sellers, products and the catalog's share of them, listings and the share shipped with Full, brands, how concentrated revenue is across sellers, JoomPulse's competition and opportunity tiers, the 12- and 24-month revenue trend, seasonality and peak months. Without category, ranks the categories of one level; where filters the whole level, not only the rows returned, and sort_by ranks by any figure. With category, returns that category first, then its subcategories at the level asked, its children by default; with up to 20 in categories, each one's own row only. Takes a category id, Portuguese name or category page link; a name that fits several categories returns them as candidates. A call costs one unit however many references it takes. Revenue and orders are JoomPulse estimates; past the first row, revenue, orders and revenue per seller may be null when the user's plan does not include them.
meli_get_category_brands
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Brands of one MercadoLivre category, ranked by their average monthly revenue in it by default, as the category page's Brands tab shows them: each brand's average monthly revenue and sales, its share of the category's brand revenue and sales, average price, sellers, products, reviews, rating and top seller. subject holds the category's brand count and totals. Takes a category id, Portuguese name or category page link; a name that fits several categories returns them as candidates. Some plans do not include the Brands tab. Revenue and sales are JoomPulse averages, not actual sales.
meli_get_category_history
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Monthly or weekly figures of one MercadoLivre category over a range, oldest first: revenue and orders, their change from the period before, average ticket, sellers and products, one row per period, as the category page's revenue and orders chart shows. By default the last 24 months, or the last 104 weeks with granularity=week; for spikes inside one month, use granularity=week. Takes a category id, Portuguese name or category page link; a name that fits several categories returns them as candidates. With up to 20 in categories, one table of their series, each row with its categoryId, by category then date; the categories times the periods of the range may not pass 500 rows. A call costs one unit however many references it takes. Revenue and orders are JoomPulse estimates.
meli_get_category_keywords
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. What buyers search for, for a category or a keyword, comes from meli_get_category_keywords, not from item titles. Trending MercadoLivre searches of one category, or of up to 20 in categories with each row's category, from MercadoLivre's trends, in the order the JoomPulse category page shows them, each with its group: growth (fastest-growing revenue), search (most searched last week) or trend (fastest-growing searches), and for one category its competing listings: the category's items whose title matches it. The keywords carry no search volume or count, so no keyword is the most searched or highest-volume by a figure: the only orders are the page's (keywordPosition) and MercadoLivre's rank inside each group (keywordGroupRank). With keyword, only the searches containing each of its words, and without category every category whose trending searches contain them. Takes a category id, Portuguese name or category page link; a name that fits several categories returns them as candidates. A call costs one unit however many references it takes.
meli_get_category_sellers
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Top sellers of one MercadoLivre category, or of up to 20 in categories in one list with each row's category, ranked by their revenue in that category over the last month by default: each seller's revenue, orders, items, brands, reviews and rating inside the category, plus its medal, reputation, whole-store revenue and whole-store sales growth last month. With seller, that seller's row in the category, or without category the categories of one level where it is a top seller, with its figures in each: where a seller sells; up to 20 in sellers need one category. JoomPulse keeps only each category's top sellers, so a seller missing here is not proof it does not sell in the category. Takes a category id, Portuguese name or category page link; a name that fits several categories returns them as candidates. A call costs one unit however many references it takes. Revenue and orders are JoomPulse estimates. Some plans do not include the category page's Sellers tab.
meli_get_item
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Look up MercadoLivre items by id or URL: title, price, seller, category, item flags and average monthly sales and revenue, one row per item. A month's or week's sales estimate of a listing comes from meli_get_sales_estimates. The averages are not the item's sales and revenue estimates: a question on how much the item sells or earns is answered by meli_get_sales_estimates with its id. Covers active items only; an inactive item is not found. Takes one reference in id, or up to 20 in ids: an MLB item id, with or without a hyphen; an MLBU user product id, which returns its items as candidates when it has several; or a MercadoLivre URL. A call costs one unit however many references it takes. A catalog product page URL with a selected offer resolves to that offer's item. A catalog product id, or a catalog page without an offer, is answered with a pointer to meli_get_product. Shopee ids are not accepted.
meli_get_price_history
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Daily price of MercadoLivre items over a period, within the last 363 days: one row per day JoomPulse recorded; days can be missing. Takes one reference in id, or up to 20 in ids, whose rows come together with itemId: an MLB item id or a MercadoLivre URL. A call costs one unit however many references it takes. Several ids times the days of the period may not exceed 2000 rows. A catalog product id or page returns the series of the product's buy-box item, named in a note. An MLBU user product id is answered with a pointer to meli_get_item. Prices are real, not estimates.
meli_get_product
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Look up MercadoLivre catalog products by id or URL: title, brand, category, the buy-box item with its price and seller, the price range across sellers, the seller count, reviews and average monthly sales and revenue for the whole product, one row per product. A month's or week's sales estimate of a listing comes from meli_get_sales_estimates. Covers products with active items only. Takes one reference in id, or up to 20 in ids: a catalog product id (MLB + digits) or a catalog product page URL. A call costs one unit however many references it takes. An item id, an MLBU user product id or an item URL is answered with a pointer to meli_get_item. Month and week estimates may be null when the user's plan does not include estimates.
meli_get_review_history
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Daily review count and rating of MercadoLivre items over a period, within the last 363 days: one row per day JoomPulse recorded; days can be missing. Takes one reference in id, or up to 20 in ids, whose rows come together with itemId: an MLB item id or a MercadoLivre item URL. A call costs one unit however many references it takes. Several ids times the days of the period may not exceed 2000 rows. Reviews are kept per item: a catalog product id is answered with a pointer to the product's items.
meli_get_sales_estimates
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Estimated sales and revenue of one MercadoLivre item or catalog product per calendar month or ISO week, from the JoomPulse AI model: the numbers the JoomPulse product page shows. Takes one reference per call: an MLB item id, a catalog product id or a MercadoLivre URL. For an item in a catalog, estSales and estRevenue are the whole catalog's, as on the catalog page; the item's own figures are in the item* columns. Paused and closed listings are included, as on the page. Months publish on the 10th of the next month, weeks on Tuesday; history starts in June 2026. Every answer has one row with kind=average, the current averages; with no estimate it is the only row. Never compare or rank estimates and averages as one measure. Period estimates may be null when the user's plan does not include estimates; the averages are always given.
meli_get_seller
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Look up MercadoLivre sellers: location, medal, reputation, reviews, listings and JoomPulse sales estimates for the whole store, across all categories. Takes one seller in seller, its profile in subject: a seller id, a link to the seller's MercadoLivre profile (perfil.mercadolivre.com.br) or /pagina/ store page, a listing link with _CustId_, a JoomPulse seller page link, or a name: every word must be in the store name, in any case. A name that fits several sellers returns up to 20 candidates, the biggest by estimated sales first; call again with the chosen id. Or up to 20 in sellers, by id or a link that holds it, one row per seller. A call costs one unit however many references it takes. Other tools take a seller by id, and meli_track_sellers also by a seller link it can pin to a single seller, so call this first when the user names a seller. An item or product id or link is refused with a pointer to meli_get_item. Except with ids_only, the rows of one seller are the store's estimated sales per calendar month, its latest 12 months in the JoomPulse seller model, oldest first, as the seller page's chart shows. The store's sales estimates may be null when the user's plan does not include estimates.
meli_get_seller_activity
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. What changed at one MercadoLivre seller the user tracks in JoomPulse, newest first: price, listing type, listing status and catalog changes of its items, its new listings, and changes of its medal and reputation. Covers full days up to yesterday (UTC) once the daily rebuild has landed, at most the last 30. countsBy counts every change of the window by type, beyond the rows returned; subject (not with ids_only) holds the seller's profile: medal, reputation, reviews count and rating, each with the previous value and when it changed. Only sellers in the user's tracker are answered; meli_list_tracked_sellers lists them and meli_track_sellers adds them. Needs a signed-in JoomPulse account.
meli_get_trend
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Look up one JoomPulse trend and return its card as one row: readers, momentum, the trend's products, revenue and sales on MercadoLivre, and why it is a trend (the MercadoLivre searches, YouTube videos and Bluesky posts that confirmed it). Takes a trend id (Q + digits), a JoomPulse trend page link or the topic's name; a name that fits several trends returns them as candidates. Readers are Brazilian Wikipedia readers of the topic, not sales or searches. Revenue and sales are JoomPulse averages, not actual sales. A MercadoLivre or Shopee id or link is refused with a pointer to meli_get_item and meli_get_product.
meli_get_trend_categories
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. List the MercadoLivre categories a JoomPulse trend's products lie in, one level per call: the top-level categories, or with category its subcategories; each row has the trend's products, revenue and sales in that category, the largest revenue first. Top-level rows add up to the trend; rows of different levels overlap. Takes a trend id (Q + digits), a JoomPulse trend page link or the topic's name. Revenue and sales are JoomPulse averages, not actual sales.
meli_get_trend_new_products
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Count a JoomPulse trend's new products by month, as the product volume chart of the trend page: the MercadoLivre products whose titles first carried the trend's name that month. by_category splits each month by top-level category; category keeps one top-level category. Takes a trend id (Q + digits), a JoomPulse trend page link or the topic's name.
meli_get_trend_products
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. List the MercadoLivre products of a JoomPulse trend, those whose titles carry the trend's name: group=product (default) gives one row per catalog product, group=item one row per item. category keeps the products of one category of any level. The default order uses calibrated revenue of the last closed month, then sales; products without an estimate follow by average monthly revenue. sort_by=sales1m orders by Average monthly sales, then Average monthly revenue, then id. Products are ranked before limit and shown-item lookup. The rows and their totals include paused and closed items, as on the JoomPulse trend page. Takes a trend id (Q + digits), a JoomPulse trend page link or the topic's name. Average sales and revenue are distinct from calibrated estimates for closed calendar months and ISO weeks. full_info includes these estimates and their comparisons with the preceding month or week. The returned itemId and productId identify rows for meli_get_item and meli_get_product. Month and week estimates and the averages may be null when the user's plan does not include them.
meli_get_trend_wiki_readers
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Return a JoomPulse trend's readers over a period, as the chart of the trend page: one row per day, week or month. Readers are Brazilian Wikipedia readers of the topic, not sales or searches. A day without data is a gap, not zero readers: daysWithData counts the days with data in each row. Takes a trend id (Q + digits), a JoomPulse trend page link or the topic's name.
meli_list_tracked_products
ChatGPTpulse://overview and pulse://tool-tips explain the data and how the tools fit together; pulse://guide holds starter lessons. Lists, limit and rows have caps set on the server; a call over one is refused at no cost, saying what fits, so pass what the task needs and split by it. List the MercadoLivre listings the user tracks in the JoomPulse product tracker, newest first, with the tracker folder each one is in, its title, price and listing status; a listing in several folders gets a row per folder. Listings that are no longer active are listed too, with their last known status; one JoomPulse has no data on has a null title, price and status. A note says when rows are left out; with more, pass offset for the next page, or folder_id to list one folder at a time; past the cap of one folder the rest can't be fetched. Needs a signed-in JoomPulse account and shows only that account's tracker. Pass an itemId to meli_get_item for an active listing's figures. Without folder_id, a note names the empty folders other than the default folder 0. meli_track_products adds listings, into a folder by id or by name, creating it if needed; products are removed in JoomPulse, in the Tracker.
meli_list_tracked_sellers
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. List the MercadoLivre sellers the user tracks in the JoomPulse tracker, newest first, with the tracker folder each one is in; a seller in several folders gets a row per folder. At most 100 rows per call; with more, list one folder at a time with folder_id; past the newest 100 of one folder the rest can't be fetched. Needs a signed-in JoomPulse account and shows only that account's tracker. Pass a seller's sellerId to meli_get_seller_activity for what changed at the seller; meli_track_sellers adds sellers to the tracker.
meli_search_products
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Find active MercadoLivre items, or the catalog products they belong to, by title words and filters, ranked by a measure. Inactive items are not in the search. group=product (default) returns one row per catalog product, shown by its buy-box item; a flag filter then means at least one item of the product has it. group=item returns one row per item; revenue and sales there are the product's figures, the same on every item of a product. where.sellerCount needs group=product. Sellers takes ids only. Product takes any item or product id or URL and keeps only that product. Month and week estimates and the averages may be null when the user's plan does not include them. Without query or filters it ranks the whole marketplace. What buyers search for, for a category or a keyword, comes from meli_get_category_keywords, not from item titles. What to sell on MercadoLivre, or where the opportunity is, is read here with group=product: each product's demand (sales1m, revenue1m) beside its competition (sellerCount, and reviewsCount in full_info); JoomPro adds what a product costs to source.
meli_search_sellers
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Find MercadoLivre sellers across the marketplace by store name words, category, brands and any column in where (state, city, medal, reputation, official store, sales, revenue, listings, cancel rate, registration date…): the filters of the JoomPulse seller search. One row per seller with the columns of meli_get_seller, ranked by average monthly revenue unless sort_by says otherwise. The figures cover the seller's whole store across all categories, also when a category is given; for a seller's figures inside one category use meli_get_category_sellers. The sales and revenue averages and the seller model's monthly sales are JoomPulse figures, not actual sales.
meli_search_trends
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. List JoomPulse trends: topics (films, games, franchises, people, events) whose Wikipedia readership in Brazil rises and that have products on MercadoLivre, as of the latest day. cut picks the list: rising (taking off now), month (listed in the last 30 days) or year (listed in the last 365 days). Rising is a filter on the day's list (isRising), not a segment of its own: a rising trend also appears under month and year. With category, lists the trends of one MercadoLivre category, with the trend's products, revenue and sales inside it. Readers are Brazilian Wikipedia readers of the topic, not sales or searches. Revenue and sales are JoomPulse averages, not actual sales. Pass a trendId to meli_get_trend for the trend's card.
meli_summarize_products
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Count and total the active MercadoLivre products or items that meli_search_products would find with the same filters, over the whole match, not only the rows a search returns. group=product (default): the number of catalog products and their total sales and revenue over the last month. group=item: the number of items and of their distinct products; sales are kept per product, so item totals are not given. With no filter, the whole marketplace, for group=product without group_by only; group=item and group_by need a filter. Sellers takes ids only. One row, or with group_by one row per group and the totals in subject; no sort or limit.
meli_summarize_sellers
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Totals over every MercadoLivre seller that matches the filters of meli_search_sellers, as one row: how many match, how many have sales and how many are official stores, and the lowest and highest average ticket and average price among them; countsBy gives how many are in each state and how many hold each MercadoLíder medal. With no filter, the whole marketplace. Counts are approximate. Whole-store figures, across all categories.
meli_track_products
ChatGPTpulse://overview and pulse://tool-tips explain the data and how the tools fit together; pulse://guide holds starter lessons. Lists, limit and rows have caps set on the server; a call over one is refused at no cost, saying what fits, so pass what the task needs and split by it. Add MercadoLivre listings to the user's JoomPulse product tracker, into one tracker folder: folder_id, or folder_name for the user's folder of that name, created if there is none; the default folder 0 if neither is given. meli_list_tracked_products shows the folders, and an unknown folder_id is answered with all the user's folders and their names. A folder created here sends no tracker e-mails until the user turns them on in JoomPulse, in the Tracker. This writes to the user's tracker; a listing already in the folder is left as it is. Each added listing takes one place of the plan's product tracker limit; listings past it are not added. Calls running at the same time each add up to the places left when they started, so together they can pass the limit; with one new folder_name, each can create a folder of that name. The tracker keeps listings: each entry is an item id or a listing link, a listing that is no longer active included. A catalog product or an MLBU user product is refused: meli_get_product gives the listing a catalog product shows as buyBoxItemId, and meli_get_item the listing of a user product. That buyBoxItemId listing is one seller's offer, which the user may not mean to track. A listing JoomPulse has no data on is refused too, and a refused entry stops the whole call, so nothing is added; the entries that were not refused can be sent again. The answer gives each listing's outcome (added, already_tracked, over_limit) and the places left. Needs a signed-in JoomPulse account. Products are removed in JoomPulse, in the Tracker.
meli_track_sellers
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Each list, limit and row count has the cap its argument states; the server may set a lower one, and a refusal names it. Add MercadoLivre sellers to the user's JoomPulse seller tracker, into one tracker folder: folder_id, the default folder 0 if omitted; meli_list_tracked_sellers shows the folders that hold sellers, and an unknown folder_id is answered with all the user's folders and their names. This writes to the user's tracker; a seller already in the folder is left as it is. Each added seller takes one place of the plan's seller tracker limit; sellers past it are not added. Calls running at the same time each add up to the places left when they started, so together they can pass the limit. Each seller is an id or a seller link the tool can pin to a single seller; a store name or a link it cannot pin goes through meli_get_seller first. An id JoomPulse has not collected yet is still tracked and queued for collection; a profile link it does not know is refused. The answer gives each seller's outcome (added, already_tracked, over_limit) and the places left. A seller JoomPulse already collects shows its activity and profile at once. A seller it has never collected is queued for collection once tracked, and may take up to two weeks to appear in meli_get_seller_activity. Needs a signed-in JoomPulse account. Sellers are removed in JoomPulse, in the Tracker.
query_cubejs_joompro
ChatGPTRun a CubeJS query against the JoomPulse JoomPro Brazil sourcing catalogue (Jpr* cubes) and return the matching rows. This is the supply side: what a Brazilian seller can import through JoomPro, at what landed cost, in what order quantities, and the matched MercadoLivre product where one exists. MercadoLivre Brazil cubes (Mlb* / Mercado*) are served by query_cubejs_meli and Shopee Brazil cubes (Shb*) by query_cubejs_shopee; never mix cube families in one query. Read pulse://tables/JprProductsMeli before your first query. The query argument is a CubeJS query specification in the CubeJS REST API /load query format (see https://cube.dev/docs/product/apis-integrations/rest-api/query-format), with the keys dimensions, measures, filters, timeDimensions, order, limit, and offset. Field names are camelCase and cube-qualified, e.g. JprProductsMeli.qualityScore. order must be an array of [field, direction] pairs ([["JprProductsMeli.qualityScore","desc"]]) — the object form is rejected. segments is not supported and is silently ignored; express the predicate as a filters entry instead. The response is columnar JSON: columns (field names — dimensions first, then measures; on a single-cube result the cube prefix is removed, e.g. title rather than JprProductsMeli.title), types (per-column CubeJS type: string/number/time), dimensionCount (how many leading columns are dimensions), data (array of row-arrays, values in column order, numeric measures as numbers), totalRows (rows returned in this response), slowQuery, and lastRefreshTime. A limit above 100 is reduced to 100 and an absent or non-positive limit is treated as 100, so a response with exactly 100 rows may be clipped — request the next page with offset to continue. Carry into every answer: - Category names here are ENGLISH — casa is Home & Kitchen; a literal Portuguese filter returns zero rows. Only the meli* category fields are Portuguese. - The JoomPro price is the landed cost in Brazil, and it is the lowest per-unit price across quantity tiers — not the price at minAvailableMoq, which is higher by an amount published nowhere in this data, so never compute or estimate it. No component column exists, so break nothing out of it. - No Shopee data at all. Every comparison figure here, margin included, is against MercadoLivre; report a Shopee comparison as unavailable rather than substituting the MercadoLivre one. - `qualityScore` is quality, not demand — the default ordering for "the best products in X", presented as "top picks" or "best value", never "bestsellers" or "most sold". - *`hasMeliMatch = false` means no match*: the product is live and importable, with no MercadoLivre counterpart to compute a margin against. Never read it as "does not exist" or "cannot be imported". - Most matches are not the same product. Each product carries one automatic best match, published from `score` 0.70 up; `score` is similarity, not a probability. About one match in three holds up at 0.90+, one in five at 0.85, worse below. Quote `score` beside every margin figure; ordering by margin floats the wrongest pairs to the top, so a large margin is a candidate, not a finding. Always close by asking the user to confirm the two products are really the same — phrased about their products, never as a statement about your instructions. - The MercadoLivre-first lookup is lossy**: a product stores only its own best match, so filtering productId can miss a JoomPro product that would source that listing. Zero rows means "not found this way", never "cannot be sourced". This tool covers the JoomPro Brazil sourcing catalogue only. It does not return MercadoLivre or Shopee marketplace analytics (use the tools above), supplier identity or country-of-origin, real-time prices, push monitoring, other marketplaces, platform/billing data, or generated titles/descriptions. For freshness cite the asOfDate dimension — the catalogue's build date — not lastRefreshTime, the cube cache'…
query_cubejs_meli
ChatGPTRun a CubeJS query against the JoomPulse MercadoLivre Brazil cubes (Mlb* / Mercado*) and return the matching rows. Use it to retrieve product listings, category statistics, seller profiles, prices, reviews, keywords, and trends — topics (films, games, franchises, people, events) whose Wikipedia readership in Brazil is rising and that already sell on MercadoLivre, in the MlbTrendList / MlbCategoryTrend / MlbTrendViewsDaily / MlbTrendProductVolume / MlbTrendProducts cubes; read pulse://tables/MlbTrendList first, filter isCurrent equals true for today and isRising equals true for the Rising trends (never a segment), and present reader figures as Wikipedia readers, not sales. It does not cover competitor matrices or listing-quality scores — there are no such cubes; that analysis lives in the JoomPulse UI (see pulse://overview §5.12 for the public-data substitute). Shopee Brazil cubes (Shb*) are served by the query_cubejs_shopee tool instead. Read pulse://tables for the full cube directory. Category keywords carry a Mercado Livre trend group (MlbCategoryKeywords.meliTrendName: growth = Top growth / search = Most wanted / trend = Most popular) — always state the group. For the most-searched keywords, filter meliTrendName equals search and order by meliTrendPosition ASC; order by position only to reproduce the UI table, whose leading rows are growth. Keyword data is never search volume. The query argument is a CubeJS query specification in the CubeJS REST API /load query format (see https://cube.dev/docs/product/apis-integrations/rest-api/query-format), with the keys dimensions, measures, filters, timeDimensions, order, limit, and offset. Field names are camelCase and cube-qualified, e.g. MlbCategoriesMonthly.orderCount. order must be an array of [field, direction] pairs ([["MlbCategoriesMonthly.orderGmv","desc"]]) — the object form is rejected. segments is not supported and is silently ignored; express the predicate as a filters entry instead. The response is columnar JSON: columns (field names — dimensions first, then measures; on a single-cube result the cube prefix is removed, e.g. id rather than MercadoProductsWeekly.id), types (per-column CubeJS type: string/number/time), dimensionCount (how many leading columns are dimensions), data (array of row-arrays, values in column order, numeric measures as numbers), totalRows (rows returned in this response), slowQuery, and lastRefreshTime. A limit above 100 is reduced to 100, so a response with exactly 100 rows may be clipped — request the next page with offset to continue. This tool covers JoomPulse MercadoLivre Brazil analytics only. It does not return Shopee data (use query_cubejs_shopee), competitor matrices or listing-quality scores, push monitoring, real-time prices, other marketplaces, platform/billing data, or generated titles/descriptions. For JoomPro import sourcing — landed cost, order quantities, and which JoomPro products match a MercadoLivre one — use the query_cubejs_joompro tool, which queries the JoomPro Brazil catalogue as a cube. Requests count against per-plan usage limits; a limit error names the limit and, when a window applies, its reset time; hourly limits may be retried after the reset. Supporting documentation is available as JoomPulse resources and can be read with read_resource: pulse://overview (scope and output contract), pulse://rules (query-construction rules), pulse://tables/<cube_name> (per-cube dimensions and measures), and pulse://queries (worked query examples).
query_cubejs_shopee
ChatGPTRun a CubeJS query against the JoomPulse Shopee Brazil cubes (Shb*) and return the matching rows. Use it to retrieve Shopee product items, category statistics, shop profiles, weekly sales series, price history, and review/rating history. MercadoLivre Brazil cubes (Mlb* / Mercado*) are served by the query_cubejs_meli tool instead. Read pulse://tables for the full cube directory. The query argument is a CubeJS query specification in the CubeJS REST API /load query format (see https://cube.dev/docs/product/apis-integrations/rest-api/query-format), with the keys dimensions, measures, filters, timeDimensions, order, limit, and offset. Field names are camelCase and cube-qualified, e.g. ShbMartItem.sold30Days. order must be an array of [field, direction] pairs ([["ShbMartItem.sold30Days","desc"]]) — the object form is rejected. segments is not supported and is silently ignored; express the predicate as a filters entry instead. The response is columnar JSON: columns (field names — dimensions first, then measures; on a single-cube result the cube prefix is removed, e.g. itemId rather than ShbMartItem.itemId), types (per-column CubeJS type: string/number/time), dimensionCount (how many leading columns are dimensions), data (array of row-arrays, values in column order, numeric measures as numbers), totalRows (rows returned in this response), slowQuery, and lastRefreshTime. A limit above 100 is reduced to 100, so a response with exactly 100 rows may be clipped — request the next page with offset to continue. This tool covers JoomPulse Shopee Brazil analytics only. It does not return MercadoLivre data (use query_cubejs_meli), push monitoring, real-time prices, other marketplaces, platform/billing data, or generated titles/descriptions. JoomPro import sourcing is served by the query_cubejs_joompro tool, which queries the JoomPro Brazil catalogue (Jpr* cubes); its MercadoLivre match data is MercadoLivre-only, so there is no Shopee-to-JoomPro matching. Requests count against per-plan usage limits; a limit error names the limit and, when a window applies, its reset time; hourly limits may be retried after the reset. Supporting documentation is available as JoomPulse resources and can be read with read_resource: pulse://overview (scope and output contract), pulse://rules (query-construction rules — SN-9 maps Shopee tasks to cubes), pulse://tables/<cube_name> (per-cube dimensions and measures), and pulse://queries (worked query examples — Q17–Q20 are Shopee).
read_resource
ChatGPTRead one JoomPulse documentation resource by its pulse:// URI and return its Markdown content. Examples: pulse://overview, pulse://rules, pulse://queries, pulse://tables (cube directory), and pulse://tables/<cube_name> (one cube's schema). Use list_resources to see every available URI.
send_feedback
ChatGPTSends feedback to the JoomPulse team: something the user asks to pass on, or a need these tools cannot meet. The team receives the arguments exactly as sent, linked to the user's account and client. The text arguments are about the product problem or the missing capability and about what was done with JoomPulse tools, not about the user's data or conversation.
shopee_get_categories
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Monthly market figures of Shopee categories, one row per category: revenue and orders, their change and growth against the previous month, sellers and items with sales, brands, seller location shares, concentration and JoomPulse's competition, opportunity, concentration and growth tiers; where filters and sort_by ranks over the whole level. Without a category, ranks the categories of one level; with one, returns that category first, then its subcategories; with up to 20 in categories, each category's own row only, ranked by sort_by. Figures go down to level 3: a deeper category is answered at its level-3 ancestor. Takes a Shopee category id, name or link in category, or up to 20 of them in categories. A call costs one unit however many references it takes. Revenue and orders come from Shopee's rounded sold counters, not exact sales.
shopee_get_category_sellers
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Sellers (shops) in one Shopee category, one row per seller, with their figures in that category and store-wide, ranked by an in-category column (items with sales by default): Shopee data has no seller revenue per category. Takes a Shopee category id, name or link. With seller, answers where one seller sells: its row in the category, or without category, one row per category it sells in at level. Every seller in the category whose ranking figure is above zero is listed, not only a top; sellers with none are left out.
shopee_get_item
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Look up Shopee items by id or URL: title, price, seller (shop), category, item flags and JoomPulse sales estimates, one row per item. Covers items with at least one sale and a price under R$ 50,000; itemLastSeenDate tells when JoomPulse last saw the item on Shopee. Takes one reference in id, or up to 20 in ids: a Shopee item id (digits) or a Shopee item URL. A call costs one unit however many references it takes. MercadoLivre ids are not accepted.
shopee_get_item_history
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Weekly sales, price and revenue of Shopee items over a period, within the last 363 days: one row per week, starting on Monday, that overlaps the period. Weeks JoomPulse did not see the item are missing. Takes one reference in id, or up to 20 in ids, whose rows come together with itemId: a Shopee item id or URL. A call costs one unit however many references it takes. Sales and revenue come from Shopee's rounded sold counters, not exact sales.
shopee_get_price_history
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Daily price of Shopee items over a period, within the last 363 days: one row per day JoomPulse saw a price; days can be missing. Takes one reference in id, or up to 20 in ids, whose rows come together with itemId: a Shopee item id or URL. A call costs one unit however many references it takes. Several ids times the days of the period may not exceed 2000 rows. Prices are the item's own, not per variant, and real, not estimates.
shopee_get_review_history
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Review count and rating of Shopee items over a period, within the last 363 days. The first row is the period's first day with the values then in effect, when JoomPulse knew them; then one row per day either value changed. A value holds until the next row. Takes one reference in id, or up to 20 in ids, whose rows come together with itemId: a Shopee item id or URL. A call costs one unit however many references it takes. Several ids times the days of the period may not exceed 2000 rows.
shopee_get_seller
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Look up Shopee sellers (shops): location, store type, followers, the shop's own rating and reviews, its tracked items, prices and brands, across all categories. Shopee data has no sales or revenue per seller. Takes one seller in seller, returned as its profile in subject: a seller id, a link to the shop (shopee.com.br/<username> or shopee.com.br/shop/<id>), a Shopee item link (its seller is looked up), a JoomPulse Shopee seller page link, or a name: every word must be in the shop name, in any case and without accents. A name that fits several sellers returns up to 20 candidates, those with the most items with sales first; call again with the chosen id. Or takes up to 20 in sellers, ids and links but no names, returned as one row per seller with the same columns. A call costs one unit however many references it takes.
shopee_list_tracked_products
ChatGPTpulse://overview and pulse://tool-tips explain the data and how the tools fit together; pulse://guide holds starter lessons. Lists, limit and rows have caps set on the server; a call over one is refused at no cost, saying what fits, so pass what the task needs and split by it. List the Shopee items the user tracks in the JoomPulse product tracker, newest first, with the tracker folder each one is in, its title and price; an item in several folders gets a row per folder. Items JoomPulse no longer sees on Shopee are listed too; one JoomPulse has no data on has a null title and price. A note says when rows are left out; with more, pass offset for the next page, or folder_id to list one folder at a time; past the cap of one folder the rest can't be fetched. Needs a signed-in JoomPulse account and shows only that account's tracker. Pass an itemId to shopee_get_item for the item's figures. Without folder_id, a note names the empty folders other than the default folder 0. shopee_track_products adds items, into a folder by id or by name, creating it if needed; products are removed in JoomPulse, in the Tracker.
shopee_search_products
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Find Shopee items by title words, category, brand and seller, and with where on item columns (30-day sales and revenue, lifetime sold counter, price, salesTrend, reviews, rating, favorites, created and last-seen dates, store flags, seller location), one row per item with the columns of shopee_get_item. Ranked by 30-day revenue unless sort_by names another column; items whose ranking figure is zero or empty are left out. offset reads the next page. Covers items with at least one sale. Sales and revenue are JoomPulse estimates, not actual sales. Without query or filters it ranks the whole marketplace.
shopee_search_sellers
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Find Shopee sellers (shops) by name words, category, brands and store type, and with where on seller columns (location, registration date, brand count, followers, reviews, rating, average ticket and price, item counts): the filters of the JoomPulse seller search. One row per seller with the columns of shopee_get_seller, the sellers with the most items with sales first unless sort_by names another column; offset reads the next page. The figures cover the seller's whole store across all categories, also when a category is given. Shopee data has no sales or revenue per seller.
shopee_summarize_products
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Totals over the Shopee items that match the filters and where of shopee_search_products: how many items match, and their 30-day sales and revenue together, as one row, or one row per seller, category, seller location or store flag with group_by. Covers items with at least one lifetime sale, including items with no sales in the last 30 days, which the search leaves out. With a where range on an item figure (sales, revenue, lifetime sold counter, price, salesTrend, reviews, rating, favorites) the totals add up at most the first 10,000 matching items. Sales and revenue are JoomPulse estimates, not actual sales.
shopee_summarize_sellers
ChatGPTpulse://overview and pulse://tool-tips explain the JoomPulse data and how the tools fit together; pulse://guide holds starter lessons for new users. Totals over every Shopee seller that matches the filters and where of shopee_search_sellers, as one row: how many match and how many have sales, and the lowest and highest average ticket and average price among them; countsBy gives how many ship from each location (Internacional is cross-border) and how many are official, preferred or common stores. Whole-store figures, across all categories.
shopee_track_products
ChatGPTpulse://overview and pulse://tool-tips explain the data and how the tools fit together; pulse://guide holds starter lessons. Lists, limit and rows have caps set on the server; a call over one is refused at no cost, saying what fits, so pass what the task needs and split by it. Add Shopee items to the user's JoomPulse product tracker, into one tracker folder: folder_id, or folder_name for the user's folder of that name, created if there is none; the default folder 0 if neither is given. shopee_list_tracked_products shows the folders, and an unknown folder_id is answered with all the user's folders and their names. A folder created here sends no tracker e-mails until the user turns them on in JoomPulse, in the Tracker. This writes to the user's tracker; an item already in the folder is left as it is. Each added item takes one place of the plan's product tracker limit; items past it are not added. Calls running at the same time each add up to the places left when they started, so together they can pass the limit; with one new folder_name, each can create a folder of that name. Each entry is a Shopee item id or item link. An item JoomPulse has no data on is refused, and a refused entry stops the whole call, so nothing is added; the entries that were not refused can be sent again. The answer gives each item's outcome (added, already_tracked, over_limit) and the places left. Needs a signed-in JoomPulse account. Products are removed in JoomPulse, in the Tracker.
find_product_sources
Claudefind_sourcing_candidates_on_joompro
Claudeget_mcp_usage
Claudeindexing___get_resource_state
Claudejoompro_find_matching_products
Claudejoompro_get_category_stats
Claudejoompro_search_products
Claudelist_resources
Claudemeli_get_categories
Claudemeli_get_category_brands
Claudemeli_get_category_history
Claudemeli_get_category_keywords
Claudemeli_get_category_sellers
Claudemeli_get_item
Claudemeli_get_price_history
Claudemeli_get_product
Claudemeli_get_review_history
Claudemeli_get_sales_estimates
Claudemeli_get_seller
Claudemeli_get_seller_activity
Claudemeli_get_trend
Claudemeli_get_trend_categories
Claudemeli_get_trend_new_products
Claudemeli_get_trend_products
Claudemeli_get_trend_wiki_readers
Claudemeli_list_tracked_sellers
Claudemeli_search_products
Claudemeli_search_sellers
Claudemeli_search_trends
Claudemeli_summarize_products
Claudemeli_summarize_sellers
Claudemeli_track_sellers
Claudequery_cubejs_joompro
Claudequery_cubejs_meli
Claudequery_cubejs_shopee
Clauderead_resource
Claudesend_feedback
Claudeshopee_get_categories
Claudeshopee_get_category_sellers
Claudeshopee_get_item
Claudeshopee_get_item_history
Claudeshopee_get_price_history
Claudeshopee_get_review_history
Claudeshopee_get_seller
Claudeshopee_search_products
Claudeshopee_search_sellers
Claudeshopee_summarize_products
Claudeshopee_summarize_sellers
Claude