Lanjing Mercado Libre Product Selection

Mercado Libre（美客多）选品数据查询与分析，通过 LinkFox 网关统一调用蓝鲸 24 个商品、官链、关键词、类目、趋势、店铺、评论、汇率与套餐用量工具，覆盖墨西哥、巴西、阿根廷、智利、哥伦比亚站点。当用户提到 Mercado Libre、美客多、蓝鲸选品、Lanjing、美客多选品、商品搜索、类目趋势、关键词热搜、流量词反查、店铺查询、评论查询、汇率、套餐用量时触发此技能。

This skill queries Mercado Libre product, catalog, keyword, category, trend, seller, review, exchange-rate, and plan-usage data through the LinkFox gateway. The gateway exposes one unified route, POST /lingdong/call, and the skill selects one of 24 supported toolName values with matching arguments.

Core Concepts

• Call only ${LINKFOX_TOOL_GATEWAY}/lingdong/call. Do not call the upstream Lanjing XP-MCP server directly, and do not ask the user for upstream secret-key / X-API-Key — upstream credentials are owned by the backend.
• The request body is always {"toolName":"...","arguments":{...}}. The script takes this whole object as a single JSON argument.
• Field names inside arguments must match references/lanjing-mercado-tool-reference.md exactly, including camelCase names such as siteId, itemId, productId, categoryId, runDate, runMonth, pageNo, pageSize.
• Read data first when presenting results. Read contentText when data is text or ambiguous. Show rawResponse only when the user asks for raw diagnostics.
• Paid tools currently cost 16000 tokens per call; free tools cost 0. Trust the backend costToken field.

Reference Files

• references/api.md: LinkFox gateway contract, request/response structure, error codes, curl example, and Feedback API.
• references/lanjing-mercado-tool-reference.md: detailed Chinese reference for the 24 Mercado Libre tools — parameters, site IDs, pagination, sorting, and billing status.

Tool Selection

User intent	Use these tools
Product detail, product sales history, product search	itemInfo, itemHistory, itemSearch
Catalog/product page detail, catalog sales history, catalog search	catalogInfo, catalogHistory, catalogSearch
Daily/monthly hot keywords and reverse traffic keywords	keywordDateSearch, keywordMonthSearch, keywordReverse
Category lookup before paid analysis	categorySearch, categorySmallSearch
Category brand, item, seller, new item, price, sales, sold-history, statistics, warehouse distribution	trendBrandTopBrand, trendBrandTopItem, trendBrandTopSeller, trendNewItems, trendPrice, trendSale, trendSoldHis, trendStatistical, trendStoreInventoryType
Seller search	sellerSearch
Product reviews	reviewSearch
Exchange rate and package usage	rateInfo, myUsage

Free tools: categorySearch, categorySmallSearch, reviewSearch, rateInfo, myUsage. All others are paid.

Parameter Guide

• toolName (string, required): one of the 24 tools above.
• arguments (object, required): the tool's parameter object. Must be a JSON object, not an array/string/number. The backend strips uId/uid/memberId and trims empty values.
• Sites: MLM (Mexico), MLB (Brazil), MLA (Argentina), MLC (Chile), MCO (Colombia — only for tools whose reference explicitly lists it).
• When the user gives a category name instead of a categoryId, call categorySearch or categorySmallSearch first, then use the returned category ID for paid trend/product/catalog tools.
• reviewSearch takes itemId only (no siteId). myUsage takes {}.
• For broad research questions, narrow paid calls with site, category, keyword, date/month, pagination, price, sales, or sorting filters. Avoid exploratory paid calls not anchored to the user's goal.

调用方式

• API 端点：POST /lingdong/call（完整参数/响应/错误码见 references/api.md）
• Python 脚本：python scripts/linkfox_lanjing_mercado_product_selection.py '<JSON 参数>' [--inline]
• 成本约束：本工具会消耗积分；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。

输出策略（脚本默认行为）：

• 始终将完整响应写入 <cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-lanjing-mercado-product-selection-<timestamp>.json（<cwd> 为脚本执行时的工作目录，在 Claude Code 里即当前项目目录；<session> 取自环境变量 SESSION_ID，按用户任务自动聚合；禁止写入 /tmp，当前目录不可写则报错）
• 响应体 ≤ 8 KB：落盘后把完整 JSON 打印到 stdout
• 响应体 > 8 KB：落盘后 stdout 只输出摘要（顶层字段、常见计数如 total/costToken、最大列表字段的长度 + 前 3 条样本）
• 加 --inline 强制全量打印到 stdout（同样落盘）

读数据建议：先看摘要判断是否足够；需要具体字段时优先用 jq或ConvertFrom-Json 从保存的 json 文件按需抽取，避免整份 JSON 进入上下文。

Usage Examples

The single JSON argument is the full payload {"toolName":...,"arguments":{...}}.

bash

# Free: search Mexico categories by name
python scripts/linkfox_lanjing_mercado_product_selection.py '{"toolName":"categorySearch","arguments":{"siteId":"MLM","searchText":"Auriculares"}}'

# Paid: product detail for a real MLM item
python scripts/linkfox_lanjing_mercado_product_selection.py '{"toolName":"itemInfo","arguments":{"siteId":"MLM","itemId":"MLM4979447466"}}'

# Free: my plan usage (no arguments)
python scripts/linkfox_lanjing_mercado_product_selection.py '{"toolName":"myUsage","arguments":{}}'

# Paid: monthly hot keywords for Brazil, 2026-06
python scripts/linkfox_lanjing_mercado_product_selection.py '{"toolName":"keywordMonthSearch","arguments":{"siteId":"MLB","runMonth":"202606"}}'

On PowerShell, wrap the JSON in single quotes the same way; if quoting is troublesome, write the payload to a file and pass it via --inline after loading, or use ConvertTo-Json to build the argument.

Display Rules

1. Present the returned data clearly without inventing unsupported business conclusions.
2. Preserve the meaning and important field names from results; translate labels only when it improves readability.
3. For large arrays or time series, summarize the visible slice and read only needed fields from the persisted JSON file.
4. For "no data" or business-level failure messages, explain that the upstream Mercado data provider returned that result; do not label it as a system outage unless the wrapper response contains an actual error.
5. Never expose internal LinkFox API keys, upstream secrets, or full sensitive raw payloads in user-facing output.

Important Limitations

• The LinkFox route is a unified backend gateway; the skill does not publish separate HTTP endpoints for each toolName.
• Required-field validation happens in the backend and is also documented in references/lanjing-mercado-tool-reference.md.
• Paid tools charge per backend invocation, even if the upstream business result is empty.
• Response shapes vary by tool. Most tools return business results as text in data; use real responses and references/api.md as the source of truth instead of forcing a single table schema.

User Expression & Scenario Quick Reference

User says	Likely action
"查这个美客多商品", "商品详情", "销量历史"	Use itemInfo or itemHistory
"搜墨西哥站耳机", "筛选商品"	Use itemSearch; use categorySearch first if only category text is known
"官链", "catalog", "目录链接"	Use a catalog* tool
"关键词热搜", "月度词", "流量词反查"	Use keywordDateSearch, keywordMonthSearch, or keywordReverse
"类目趋势", "新品机会", "销量分布", "品牌排行"	Resolve categoryId, then use a trend* tool
"店铺", "seller"	Use sellerSearch
"评论", "reviews"	Use reviewSearch
"汇率", "套餐用量"	Use rateInfo or myUsage

Feedback

Auto-detect and report feedback via the Feedback API when the skill behavior, documentation, or result presentation does not match the user's intent, when the user expresses praise or dissatisfaction, or when a concrete improvement is visible. Follow references/api.md; do not interrupt the user's task and do not report secrets, private data, or complete large responses.

---

For more high-quality, professional cross-border e-commerce skills, visit LinkFox Skills.