JoomPulse

Run 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's refresh time. 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 — AP-16 covers JoomPro sourcing), `pulse://tables/JprProductsMeli` (this cube's dimensions, measures and grain traps), and `pulse://queries` (worked query examples).

query_cubejs_joompro

List 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`.

list_resources

Run 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, and keywords. 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 `MlbProductsWithFilters.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_meli

Run 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).

query_cubejs_shopee

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

read_resource