linkfox-wb-mercado-selection

[!IMPORTANT] This Skill must rely on the MCP "LinkFox". If this MCP is not installed, please clearly notify the user: Please install the LinkFox connector first:

• In WorkBuddy, find "Experts · Skills · Connectors" → "Connectors" on the left side;
• Search for the keyword "LinkFox" and install the connector "LinkFox" (note: it is linkfox, not linkfox-product-selection), and complete the login authorization according to the instructions;
• Return to WorkBuddy and retry.

LinkFox Mercado Libre Product Selection

Provides unified data query capabilities for Mercado Libre product selection and market research: auditable raw results can be obtained from dimensions such as products/official links, keywords, categories, trends, stores, reviews, site exchange rates and personal package usage, and data comparisons are given according to user goals. Currently includes 1 sub-capability identifier linkfox-mercado-product-selection, 1 exact MCP toolName and 24 downstream operations; the billing status is subject to the returned charged/costToken .

Capability boundaries

Capability scope

• Product research: use itemInfo to query basic product information, use itemHistory to query sales history, use itemSearch to filter products by conditions such as site, keyword, category, price, sales, rating, reviews, weight, listing time, warehousing, store type and sorting; uniformly call the original endpoint through LinkFox.proxy_call Call the original endpoint /mercado/productSelection, and the sub-capability identifier is linkfox-mercado-product-selection。
• Official link/catalog research: use catalogInfo、catalogHistory、catalogSearch to query basic information, sales history and filtering results of official links or catalogs;catalogSearch supports conditions such as keyword, category, brand, price, sales, rating, inventory, weight, BSR, warehousing, store type, status, month and days since listing.
• Keyword research: use keywordDateSearch to get hot search terms for a specified date, use keywordMonthSearch to get hot search terms for a specified month, use keywordReverse to reverse-lookup traffic terms for products; the date format is YYYYMMDD, and the month format is YYYYMM。
• Category positioning: use the free categorySearch to search categories, use the free categorySmallSearch to search the smallest subcategory; when the user only has a category name, resolve categoryIdfirst, and then call the paid product, official link or trend operation.
• Category trends and opportunities: use trendBrandTopBrand、trendBrandTopItem、trendBrandTopSeller to query brand/product/store rankings, use trendNewItems to analyze new product opportunities, use trendPrice to query price distribution, use trendSale to query sales distribution, use trendSoldHis to query sales history, use trendStatistical to query category summary statistics, use trendStoreInventoryType to query warehousing type distribution; these operations all require siteId and categoryId。
• Stores and user feedback: use sellerSearch to search stores by site, store type, level and quality seller level; use the free reviewSearch to get product reviews by itemId .
• Site and quota information: use the free rateInfo to query site currency exchange rates against USD and CNY, use the free myUsage to query the current plan and usage; both operations are still executed through the same MCP endpoint.
• Result traceability: retain the actual MCP toolName, downstream operation, business parameters, query context, and audit fields in the response; the old script's local cache, automatic disk persistence, session metadata, and stdout summary are not MCP capabilities.

Boundaries and Limitations

• Invocation boundary: use only LinkFox.proxy_call, with the exact toolName being mercado/productSelection; do not connect directly to the legacy gateway or the upstream XP-MCP.
• Authentication boundary: WorkBuddy automatically injects the authorization context; it is forbidden to request or pass in headers, Authorization, API Key, token, JWT, phone number, or upstream credentials. Handle exceptions such as MCP and 401/402 according to references/onboarding.md .
• Site boundary：MLM is Mexico,MLB is Brazil,MLA is Argentina,MLC is Chile;MCO is Colombia, but use it only when the reference documentation for each operation explicitly supports it.reviewSearch accepts only itemId, do not pass siteId；myUsage use an empty object parameter.
• Billing boundary：categorySearch、categorySmallSearch、reviewSearch、rateInfo、myUsage is a free operation; for other operations, the current backend usually returns costToken = 16000for each call, and billing may occur even if the business result is empty. The same MCP toolName + arguments must not be called repeatedly within the same task; on failure or empty results, do not automatically try different wording, page through, or change parameters for continuous probing.
• Parameter boundary: the original downstream request body must be {"toolName":"<operation>","arguments":{...}}, placed entirely into proxy_call.arguments; the business arguments must be an object, and field names must strictly use the casing in the reference documentation. The backend removes uId、uid、memberId and trims empty values, but do not rely on these fields to complete business calls.
• Data boundary: for most operations, data is formatted text, so do not force the assumption that all results are a uniform array; read datafirst, read contentTextonly when the user requests diagnostics. rawResponse。
• Out-of-scope: does not provide Mercado Libre store login, Listing publishing, order/inventory changes, ad placement, logistics fulfillment, supply chain procurement, platform appeals, or legal/financial conclusions; do not package data query results as definitive sales guarantees, profit guarantees, or platform rule conclusions.

Tool Selection Guide

Need / User says	Default recommendation	When to switch to another
"Look up this Mercado Libre product" "View product details"	itemInfo	For sales changes use itemHistory; to find a batch of products by criteria use itemSearch
"Search Mexico site for headphones" "Filter competitors"	itemSearch	If you only have a category name, first use categorySearch/categorySmallSearch; if you already have product IDs, use itemInfo or itemHistory
"Look up official link/catalog link"	catalogInfo	For official link sales history use catalogHistory; for batch filtering use catalogSearch
"Look up hot search terms" "View monthly terms"	keywordDateSearch or keywordMonthSearch	If there is a specific date, use daily; if there is a specific month, use monthly; to get the traffic terms brought by a product use keywordReverse
"View this product's traffic terms"	keywordReverse	Must have itemId; to research site-wide demand, use daily/monthly hot search terms instead
"Category Trends" "Brand/Product/Store Rankings"	First categorySearch, then select by goal trend*	For new products choose trendNewItems, for price choose trendPrice, for sales distribution choose trendSale, for history choose trendSoldHis, for summary choose trendStatistical, for warehousing choose trendStoreInventoryType
"Find opportunity categories/View category size"	trendStatistical or trendNewItems	When only category text is available, first call the free category search; when price bands or warehousing structure are needed, switch to the corresponding trend operation
"Look up stores" "View reviews"	sellerSearch or the free reviewSearch	For store research use sellerSearch; if you already have a product ID and want buyer feedback, use reviewSearch
"Check exchange rate" "See how much of the plan remains"	The free rateInfo or myUsage	Exchange rate must include siteId; for plan usage, arguments is fixed to {}

When selecting, first determine whether the user wants a single object, list filtering, keywords, category trends, or auxiliary information, then verify required fields and site support scope. When multiple operations can answer, prefer the option whose returned information best matches the goal and requires the fewest calls; first use free category parsing to reduce uncertainty in paid calls. Before a paid call, make clear that the current result may incur credit consumption, and whether to continue is up to the user.

Business Requirement Routing Quick Reference

Sub-capability	Business capability	reference	Original endpoint	Exact MCP toolName
linkfox-mercado-product-selection	itemInfo Product basic information (paid)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	itemHistory Product sales history (paid)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	itemSearch Product search filtering (paid)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	catalogInfo Official link basic information (paid)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	catalogHistory Official link sales history (paid)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	catalogSearch Official link search filtering (paid)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	keywordDateSearch Daily hot search terms (paid)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	keywordMonthSearch Monthly hot search terms (paid)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	keywordReverse Product traffic keyword reverse lookup (paid)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	categorySearch Category search (free)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	categorySmallSearch Smallest subcategory search (free)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	trendBrandTopBrand Category brand ranking (paid)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	trendBrandTopItem Category product ranking (paid)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	trendBrandTopSeller Category store ranking (paid)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	trendNewItems New product opportunities (paid)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	trendPrice Price distribution trend (paid)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	trendSale Sales distribution (paid)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	trendSoldHis Sales history trend (paid)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	trendStatistical Category summary statistics (paid)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	trendStoreInventoryType Warehousing type distribution (paid)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	sellerSearch Store search (paid)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	reviewSearch Product reviews (free)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	rateInfo Site exchange rate (free)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection
linkfox-mercado-product-selection	myUsage Plan and usage (free)	references/linkfox-mercado-product-selection.md	/mercado/productSelection	mercado/productSelection

Detailed required/optional parameters, site and pagination rules are consolidated in references/mercado-tool-reference.md; gateway contract and error codes are in references/api.md; authentication and plan guidance are in references/onboarding.md. Sub-capability archive index is in references/linkfox-mercado-product-selection.md。

MCP Invocation Method

• MCP server：LinkFox; unique tool:proxy_call。
• Exact endpoint toolName：mercado/productSelection, i.e., the original endpoint /mercado/productSelection with the leading /; case-sensitive, must not be replaced with the 24 operation names.
• Shared proxy parameters：proxy_call.arguments must be the original downstream request body, i.e. {"toolName":"<operation>","arguments":{...}}. The first layer toolName is the MCP endpoint, and the inner arguments.toolName is one of the 24 operations; business fields remain in arguments.arguments, and must not be flattened or wrapped again in body/params/data。
• Automatic authorization: WorkBuddy automatically injects the authorization context; adding headers, Authorization, API Key, token, JWT, phone number, or other credentials to MCP configuration and call parameters is prohibited.
• Response parsing: first check the MCP connection, tools, schema, and isError, then read the text/structured content; when text is a JSON string, parse it only once. Then check the downstream errcode/errmsg、code/msg, and finally read the data、contentText、total、charged、costToken、costTime。
• Deduplication and error layering: within the same task, the same MCP toolName + arguments is called only once. When a paid call fails, returns empty results, or is unsatisfactory, do not automatically retry, reword, paginate, or change parameters; if additional calls are needed, first explain the potential consumption and obtain user consent. When MCP is unavailable, falling back to the legacy HTTP gateway, scripts, or other tools is prohibited.
• Local capability changes: the legacy script's 24-hour cache, automatic response persistence, session metadata, and stdout summaries have been removed; do not claim that MCP automatically provides these capabilities. When presenting, base it directly on the visible data returned by this MCP call, and record the query context.
• Full parameter locations：references/api.md describes the shared MCP request, unified response, and error codes;references/mercado-tool-reference.md records the required/optional fields, sites, pagination, sorting, and upstream protocol codes for the 24 operations;references/linkfox-mercado-product-selection.md is the sub-capability index; for authentication and credit anomalies, see references/onboarding.md。
• Feedback: the Feedback API is independent of the tool endpoint; when actual behavior does not match user intent or the user provides feedback proactively, you may report concise and desensitized content according to references/api.md , without interrupting the business call, and without uploading credentials, privacy, complete large responses, or sensitive data.

Usage examples

The following are all complete proxy_call parameters. Before executing a paid operation, first explain that credit consumption may occur;costToken、charged and the returned business results are subject to the actual MCP downstream response.

1. Locate the category first (free)

{
  "toolName": "mercado/productSelection",
  "arguments": {"toolName":"categorySearch","arguments":{"siteId":"MLM","searchText":"Auriculares"}}
}

Use the returned category ID to continue calling trends or product filtering; when the finest level is needed, use categorySmallSearchinstead, and the required field is still siteId、searchText. Usually returns data text and costToken: 0。

2. Product details, history, and filtering (paid)

{
  "toolName": "mercado/productSelection",
  "arguments": {"toolName":"itemInfo","arguments":{"siteId":"MLM","itemId":"MLM4979447466"}}
}

Product history only requires itemId：

{
  "toolName": "mercado/productSelection",
  "arguments": {"toolName":"itemHistory","arguments":{"itemId":"MLM4979447466"}}
}

When filtering by conditions, keep siteId, and add the remaining filter fields as needed:

{
  "toolName": "mercado/productSelection",
  "arguments": {"toolName":"itemSearch","arguments":{"siteId":"MLM","title":"Auriculares","priceBegin":200,"priceEnd":1500,"sale30Start":10,"sortKey":"sale30d","sortOrder":"desc","pageNo":1,"pageSize":50}}
}

The result may be formatted text; do not assume that data is necessarily a unified array. Paid calls may be billed even when there are no matching results.

3. Official link/catalog queries (paid)

{
  "toolName": "mercado/productSelection",
  "arguments": {"toolName":"catalogInfo","arguments":{"siteId":"MLB","productId":"MLB21333"}}
}

Use the following for batch filtering:

{
  "toolName": "mercado/productSelection",
  "arguments": {"toolName":"catalogSearch","arguments":{"siteId":"MLB","searchText":"fones bluetooth","priceVolStart":50,"priceVolEnd":500,"sales30VolStart":10,"sortKey":"sale30d","sortOrder":"desc","pageNo":1,"pageSize":50}}
}

catalogHistory Use siteId and productId to query official link history; do not mix official link IDs with regular product itemId .

4. Keyword demand and traffic keywords (paid)

By day:

{
  "toolName": "mercado/productSelection",
  "arguments": {"toolName":"keywordDateSearch","arguments":{"siteId":"MLM","runDate":"20260601","pageNo":1,"pageSize":50}}
}

By month:

{
  "toolName": "mercado/productSelection",
  "arguments": {"toolName":"keywordMonthSearch","arguments":{"siteId":"MLB","runMonth":"202606"}}
}

Reverse lookup when a product ID is already available:

{
  "toolName": "mercado/productSelection",
  "arguments": {"toolName":"keywordReverse","arguments":{"siteId":"MLM","itemId":"MLM4979447466"}}
}

Daily/monthly queries support filtering, sorting, and pagination; some keyword operations have a maximum pagination depth of 10000, and additional consumption must be evaluated before continuing to paginate.

5. Category trends and opportunities (paid)

First obtain from the free category query categoryId, then select a trend operation based on the question. For example, brand ranking:

{
  "toolName": "mercado/productSelection",
  "arguments": {"toolName":"trendBrandTopBrand","arguments":{"siteId":"MLM","categoryId":"MLM458037"}}
}

Example of new product and monthly sales distribution:

{
  "toolName": "mercado/productSelection",
  "arguments": {"toolName":"trendNewItems","arguments":{"siteId":"MLM","categoryId":"MLM458037"}}
}

{
  "toolName": "mercado/productSelection",
  "arguments": {"toolName":"trendSale","arguments":{"siteId":"MLM","categoryId":"MLM458037","month":"202606"}}
}

trendBrandTopItem、trendBrandTopSeller、trendPrice、trendSoldHis、trendStatistical and trendStoreInventoryType likewise require at least siteId、categoryId; the latter two can be added per the reference documentation month。

6. Stores, reviews, exchange rates, and usage (free/paid)

Store filtering is a paid operation:

{
  "toolName": "mercado/productSelection",
  "arguments": {"toolName":"sellerSearch","arguments":{"siteId":"MCO","sellerType":"LOCAL","levelId":"5_green","pageNo":1,"pageSize":50}}
}

Product reviews do not require siteId, and are a free operation:

{
  "toolName": "mercado/productSelection",
  "arguments": {"toolName":"reviewSearch","arguments":{"itemId":"MLM4979447466","pageNo":1,"pageSize":50}}
}

Exchange rates and plan usage:

{
  "toolName": "mercado/productSelection",
  "arguments": {"toolName":"rateInfo","arguments":{"siteId":"MLM"}}
}

{
  "toolName": "mercado/productSelection",
  "arguments": {"toolName":"myUsage","arguments":{}}
}

MCO may only be used for operations explicitly listed in the reference documentation; plan usage identifies the user from the authentication information—do not fabricate a user ID.

Display rules

1. Objective presentation: prioritize presenting the data、contentText、total、charged、costToken and costTimereturned by the gateway; do not expand query results into unsupported sales, profitability, or market conclusions.
2. Label the context: when displaying lists or trends, label the toolName, site, category/product ID, date or month, filter conditions, pagination range, and query time, so users can verify.
3. Text-first parsing：data is mostly text; when structure is needed, first determine textParsedAsJson, then extract according to the actual return. For large arrays or time series, show only the currently visible slice and necessary statistics; do not fabricate complete results that are not visible.
4. Distinguish errors from empty results：code: "200" and data means "no product/review found" etc., which is an upstream business no-result, not a system failure; only MCP errors or non-200 errcode are treated as errors.
5. Correction suggestions：errcode: 1002 , check the inner operation, business parameter object, required fields, field case, site, and date format;errcode: 500 , record desensitized information and do not automatically retry paid calls.
6. Cost transparency: paid results show the charged and costTokenreturned by the gateway, and remind users that paid operations are billed per call and empty results do not mean no charge; free operations should not be marked as paid.
7. Sensitive information protection: do not display API Keys, upstream secrets, JWTs, phone numbers, internal authentication responses, or complete sensitive raw payloads; when users request raw diagnostics, provide only the necessary and desensitized fields.
8. Feedback reporting: when there is a clear experience deviation, praise, dissatisfaction, or a reproducible improvement point, use the Feedback API of references/api.md with skillName, sentiment, category, and concise content to report; do not interrupt the current task, and do not include privacy or credentials.

Resolve authentication and credit issues

When the following abnormal situations occur, read references/onboarding.md and handle them according to the process therein; do not guess on your own or ask for credentials.

Abnormal situations

• MCP or proxy_call missing: stop business calls, prompt to check the LinkFox configuration and reload WorkBuddy; HTTP fallback is prohibited.
• 401 / authorized error: handle as a WorkBuddy automatic authorization chain exception, prompt to log in again or reload the connection; do not request or re-submit the Key. Do not treat 401 as insufficient credits.
• 402 / insufficient credits or balance: When the message contains meanings such as "insufficient points balance", "insufficient billing", "insufficient balance", "quota exceeded", "insufficient balance", "package expired", "recharge required", "please recharge", read the package list and let the user choose; do not purchase automatically.
• 403: This is a permissions issue and is not classified under authentication or billing guidance; handle it based on the returned information and do not pass authentication fields.

Guidance Rules

For MCP or authorization exceptions, only prompt the user to log in again, reload the connection, or contact the WorkBuddy administrator. When points are insufficient, guide the user to visit https://agent.linkfox.com/ for self-service handling; do not automatically query packages, select packages, create payment orders, pay, or poll. Whether to re-initiate the business call after handling is complete is decided by the user.

Points Consumption Notice

Users will pay fees due to points consumption. Please fully assess: when this skill needs to be called frequently, or when the user has insufficient expectation of the points consumption amount, be sure to remind the user, and let the user decide whether to continue.