Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

amazon-comments-crawling

Scrape Amazon product reviews by URL to collect customer comments for analysis; keyword searches are not supported.

Instructions

Scrape comments for a specified product on Amazon. Important: provide the product URL; keyword searches are not supported.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "amazon-comments-crawling"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAmazon product URL to scrape reviews from. Example: https://amazon.com/Roku-Express-Streaming-Wireless-Controls/dp/B0916TKFF2/
env_idsNoOne or more environment IDs where this task should run. If the user did not provide environment details (name, id, remark, serial number), prompt for them or offer to help create an environment.
maxReviewsNoMaximum number of reviews to scrape.
run_timeoutNoOverall process timeout in seconds. The environment will be closed automatically after this period.
is_cancel_closeNoShould the environment be closed after the execution is completed? 0 means close, 1 means do not close. The default is 0. If you set it to 1, please set run_timeout to 0 to avoid automatic closing due to timeout.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, yet it says nothing about side effects: the tool evidently spawns a task in an environment, can auto-close that environment, and is governed by a timeout. Those traits appear only in the parameter schema, and the description does not mention rate limits, authentication, or that execution is asynchronous.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core action and followed immediately by the most likely failure mode. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter scraping task with environment lifecycle and timeout semantics, the description covers only the input shape and the URL constraint. The schema fills most gaps, but an agent gets no description-level signal about what is returned or how the task lifecycle behaves.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter including env_ids, maxReviews, run_timeout and is_cancel_close is already documented. The description only reinforces the url parameter by ruling out keyword input, adding little beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Scrape comments for a specified product on Amazon'), which is enough to identify the tool without opening the schema. It does not explicitly contrast with the sibling youtube-comments-scraper, but the Amazon scope is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear usage constraint: a product URL is required and keyword searches are not supported, which steers the agent away from a plausible wrong invocation. It stops short of naming alternatives or stating prerequisites such as environment availability.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.