linkfox-ehunt-etsy-store-query

EHunt Etsy shop query (_ehunt_storeQuery）

When the LinkFox "Third-Party Data Service" MCP is available, call by tool name _ehunt_storeQuery (MCP display name:Etsy店铺查询, subject to the tool metadata issued in the current environment). Authentication and upstream routing are handled by the gateway; if the response contains a root-level code field, whether it succeeds is subject to the live network.

Key points

• Pagination：page starts from 1;pageSize defaults to 20, maximum 100.
• Range parameters：begin* / end* correspond in pairs to the upstream comma range; when only one side is filled, the upstream is "start~" or "~end".
• Sorting：sortBy only 8~11(8 total sales, 9 weekly sales, 10 review count, 11 favorites count).sortDesc：1=descending, 0=ascending(do not confuse with the product API's sortDesc ).

Script (optional)

Command-line debugging:python scripts/ehunt_etsy_store_query.py '<JSON>'(requires LINKFOXAGENT_API_KEY). See details at the end of references/api.md .

Reference

For the input/output parameter table, see references/api.md。

Handling Large Responses

To avoid overflowing the agent context, persist the response to disk and extract only the fields you need:

python scripts/response_io.py run --script scripts/ehunt_etsy_store_query.py --out-dir <DIR> '<params>'
python scripts/response_io.py read <file> --fields "<paths>"   # or --path "<JMESPath>"

Pick --out-dir outside any git working tree (e.g. /tmp/... on Unix, %TEMP%/... on Windows). Persisted responses may contain PII, pricing, or auth-sensitive data — do not commit them. Files are not auto-deleted; clean up when the task is done.

run writes the full response to a file and emits only a schema preview + file path. read projects specific fields, with --limit/--offset for slicing and --format json|jsonl|csv|table for output.

When to prefer this pattern — apply your judgment based on the response characteristics, e.g.:

• High field count per record, or fields you don't need
• Batch/paginated results (multiple items per call)
• Long-text fields (descriptions, reviews, HTML, time series)
• Output reused across later steps rather than consumed immediately

For small, single-use responses, calling the main script directly is fine.

⚠️ The preview is a truncated schema + sample, not the full data. Any field-level decision must read from the persisted file via read.