跳到正文
cccskills
免费在 GitHub 公开

apify-product-lookup

Look up current product prices, stock, ratings, and image URLs from retailer pages through Apify. Return the results as structured fields, with retrieval time and source links, for checking a product or comparing stores.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Fetch a real product's current price, stock, rating, or images from retailer pages over the Apify MCP server, and return them as typed fields rather than prose. Use when someone asks what a product costs right now, whether it is in stock, how it is rated, to compare a product across retailers, or to check a product URL they pasted. Also use when an agent would otherwise answer a product question from training data. Not for managing your own store's catalog, not for payments, and not for questions answerable without live retailer data.

查看安装方法

适用场景

  • Check the current price and stock of a product URL
  • Compare the same product across retailers
  • Find products within a specified budget
  • Retrieve product ratings and image URLs

包含的文件(1)

  • SKILL.md5.7 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Apify product lookup

A model answers product questions from training data that was fixed months ago, or by reading a page as prose with no product fields. This skill routes the question to a hosted Actor that reads retailer pages on request and returns structured records: price, currency, stock, rating, image URLs, and a link.

Written by a product marketing manager at Apify. It calls E-commerce Scraping Tool, a paid first-party Apify Actor, so weigh the framing accordingly. Everything below is what testing against the live Actor returned, including where it does not work.

Setup

The MCP endpoint is https://mcp.apify.com. Appending ?tools=apify/e-commerce-scraping-tool narrows the server to this one Actor, which makes tool selection more reliable when product data is the only job. Authentication is OAuth on first use for interactive clients, or a bearer token for unattended ones. An Apify account is required and the Actor is paid, billed per run started plus per product returned.

Pick the input before calling

The questionInput to send
About a specific page the user gave youdetailsUrls: [{"url": "..."}]
"Find me an X under $Y" with no URLkeyword plus marketplaces
"Compare X across stores"keyword plus several marketplaces

Always send maxProductResults and additionalProperties: true. Without the second, stock, rating, list price and identifiers are all missing, because they are nested there rather than at the top level.

The call is two steps, sometimes three

  1. Call apify--e-commerce-scraping-tool (two hyphens, not a slash). It returns run metadata and a datasetId. It does not return products.
  2. Check status. If it is not SUCCEEDED, call get-actor-run with the runId and a waitSecs until it is. The Actor tool returns when its own wait window elapses, not when the run finishes, so RUNNING is a normal answer and the dataset holds nothing at that moment.
  3. Call get-dataset-items with the datasetId, a limit, and fields.

Two failures live here. Stopping after step 1 returns a result that reads like success and holds no product data. Skipping step 2 fetches an empty dataset and reports the product as not found, intermittently, depending only on how fast the retailer answered.

Project with fields, and read them defensively

The full record is large: one Amazon product measured about 88 KB across 142 fields, most of it marketing content and review text. Pass fields in dot notation, naming only what the question needs.

Projected output comes back flat. The dots stay in the key names, so it is item["offers.price"], not item["offers"]["price"]. Walking the nested path against a projected response finds nothing, which is indistinguishable from the retailer not reporting the field.

The four differences that bite hardest:

  • offers.price is a number on some retailers and a string on others.
  • Currency is offers.priceCurrency on some and offers.currency on others, and the value may be a symbol or an ISO code.
  • Stock and rating live under additionalProperties, as inStock and stars, not at the top level. Top-level rating was null on a product whose stars was 4.2.
  • brand frequently carries marketing text such as Visit the Sony Store rather than a brand name.

Answer honestly

  • Say when the data was read. The point of the call is that the answer is current, so make that visible.
  • Never claim a product is unavailable because stock was absent. Many retailers do not report it. Absent means unknown.
  • If every field comes back empty, suspect the URL before the retailer. An unresolvable URL returns an item with no fields rather than an error.
  • Quote the source URL so the user can check it.

Scope and limits

  • Latency is high and unstable. Measured end to end over MCP across twenty questions: 14.7s fastest, 24.1s median, 95.8s slowest. Treat a runtime call as verification before the user acts, not as something to put inside every turn.
  • The marketplaces enum arrives truncated over MCP, because the server caps how many characters of a long enum it forwards. Measured on 2026-08-27: of 249 values, 122 fit and 127 were dropped. A validation error naming marketplaces means the retailer cannot be named in a keyword search on this connection, not that it is unsupported. Use detailsUrls, which takes arbitrary URLs and is unaffected.
  • Field coverage is a property of the retailer, not the tool. On one measured run, Amazon returned 44 keys under additionalProperties and two other retailers returned 4, with stock and rating absent on every record from one of them. There is no unified schema to rely on.
  • Cost. Cap with maxProductResults. Prefer one call with several URLs or marketplaces over several calls, and never re-run to check a result you already have.
  • additionalProperties can reach roughly 100 KB for one product. Never paste it into a reply.
  • A rating or stars of 0 means absent, not a zero-star product.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Handle ActiveCampaign contact and marketing tasks through Rube MCP, a connection for agent tools. Find or create contacts, manage tags and subscriptions, enroll contacts in existing automated workflows, and create follow-up tasks.

中文简介正在准备中。当前显示英语简介。

  • Finding or registering contacts
  • Adding or removing contact tags
  • Subscribing contacts to lists or unsubscribing them
davepoon/buildwithclaude36712026年10月20日 更新

Research competitors’ live Meta and Google ads to identify opening hooks, offers, calls to action, and landing pages. Receive a sourced creative brief and up to three test ideas adapted to your product.

中文简介正在准备中。当前显示英语简介。

  • Find angles for new ad copy
  • Plan creative tests using competitor ads
  • Choose a landing page message
davepoon/buildwithclaude36712026年10月20日 更新

Add website or app tracking, then use command-line tools to review traffic, signups, drop-off, and returning users across projects. Run A/B tests, which compare alternative headlines or buttons, and inspect results to guide changes.

中文简介正在准备中。当前显示英语简介。

  • Adding page-view and key-action tracking
  • Reviewing traffic and referral sources across projects
  • Finding where visitors drop out before signup or purchase
davepoon/buildwithclaude36712026年10月20日 更新

Establish rules for when an AI agent should recall past context and save lasting decisions, corrections, preferences, and failures. Works with Markdown files or memory services, preserving decision history and surfacing conflicting records.

中文简介正在准备中。当前显示英语简介。

  • Carry project conventions into the next session
  • Save user corrections and lasting preferences
  • Record failed approaches and their causes
davepoon/buildwithclaude36712026年10月20日 更新

Audit local AI coding-agent sessions with agenttrace to identify spending, token use, tool failures, and operational problems. Produce readable or structured reports and define pass-or-fail thresholds for automated continuous integration checks.

中文简介正在准备中。当前显示英语简介。

  • Investigating session costs and token waste
  • Finding repeated tool failures and retries
  • Exporting session reports as Markdown or JSON
davepoon/buildwithclaude36712026年10月20日 更新

Audit saved agent sessions for access to private files and evidence that secret values entered an agent's context. Get findings without displaying secrets, identify keys needing rotation, and inspect Claude Code or Codex sessions in a local report.

中文简介正在准备中。当前显示英语简介。

  • Check whether an agent accessed .env files
  • Identify keys that may need rotation
  • Audit private-file access by subagents
davepoon/buildwithclaude36712026年10月20日 更新

查看 davepoon 的全部技能

报告此技能的问题