JoomPulse

`pulse://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_product

`pulse://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_review_history

`pulse://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_sales_estimates

`pulse://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

`pulse://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_seller_activity

`pulse://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

`pulse://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_get_trend_wiki_readers

`pulse://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_categories

`pulse://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_new_products

`pulse://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_products

`pulse://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_categories

`pulse://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_category_sellers

`pulse://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 sales figures, 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. Sales and revenue come from Shopee's rounded sold counters, not exact sales.

shopee_get_item

`pulse://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_item_history

`pulse://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, as Shopee listed them.

shopee_get_price_history

`pulse://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_review_history

`pulse://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_get_seller

List the JoomPulse hint documents — each entry gives a `pulse://` URI, a short label, and a one-line summary. Use the returned URIs with `read_resource`; `pulse://guide` holds the starter lessons for new users. A request to schedule or repeat a report needs no data call, as JoomPulse cannot schedule: where the client cannot either, Lesson 6 of `pulse://guide` gives the ready prompt, and its Check a listing recipe covers a request to check, audit or review the user's own listing; a question on why an item sells or how it compares stays on the data tools.

list_resources

`pulse://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_list_tracked_sellers

Read one JoomPulse hint document by its `pulse://` URI and return its Markdown content. We advise reading `pulse://overview` (what the data is) and `pulse://tool-tips` (how the tools fit together) before the first call. Answers are written in the language of the user's question, even when the data is in Portuguese. A user who asks what this MCP can do or how to use it, in any words or language, gets starter lessons from `pulse://guide`: read it first and answer with its welcome message only. A request to schedule or repeat a report needs no data call, as JoomPulse cannot schedule: where the client cannot either, Lesson 6 of `pulse://guide` gives the ready prompt, and its Check a listing recipe covers a request to check, audit or review the user's own listing; a question on why an item sells or how it compares stays on the data tools. Use `list_resources` to see every available URI.

read_resource

`pulse://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_search_products

`pulse://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_products

`pulse://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_sellers

`pulse://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_search_trends

`pulse://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 come from Shopee's rounded sold counters, not exact sales. Without query or filters it ranks the whole marketplace.

shopee_search_products

`pulse://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_search_sellers

Sends 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.

send_feedback

`pulse://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_products

`pulse://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_summarize_sellers

`pulse://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 come from Shopee's rounded sold counters, not exact sales.

shopee_summarize_products

`pulse://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_summarize_sellers