Asin MCP Server

Change alerts and checks

update_product

Update a tracked product's target price, drop alerts, check interval, or paused status by product ID, changing only the settings that need modification.

Instructions

Change alerts and checks. Target price, drop alerts, check interval, or pause. Send only what changes.

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": {
      "id": "<id>"
    },
    "name": "update_product"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	product_id returned when the product was added
`paused`	No	Stop checking (and charging) for now; false resumes
`target_price`	No	Email the owner when the price goes at or below this amount. null removes it.
`alert_on_drop`	No	Email when the price drops or the product is back in stock
`interval_minutes`	No	Minutes between two checks (1440 = daily). Checks faster than daily need a plan or a credit pack: every 60 minutes with a pack or Starter, 30 with Pro, 5 with Business. Default: 1440.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the mutation/safety profile is known. The description adds one genuine behavioral fact beyond them: this is a patch-style update where omitted fields are untouched. It does not mention that interval changes can trigger billing/plan requirements or what happens on invalid values, though the schema covers the plan tiers.

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

Conciseness4/5

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

Three short, front-loaded sentences: purpose, field coverage, and the partial-update rule, with no filler. It is efficient, though the field enumeration slightly duplicates the schema.

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

Completeness4/5

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

With five fully documented parameters, annotations covering the mutation profile, and no output schema to explain, the description covers what an agent needs to invoke it correctly. The only gap is routing guidance against the many sibling tools that also act on a product.

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% and every parameter carries a substantive description, including the null-removes-target-price and interval plan semantics, so the baseline is 3. The description's field list only restates what the schema already documents in more detail; it adds no format or constraint information of its own.

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 verb 'Change' targets a specific resource scope — the product's alerts and checks — and the second sentence enumerates the mutable fields (target price, drop alerts, interval, pause). An agent can tell this is not the same as track_product or get_product. It stops short of naming a sibling it must not be confused with.

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

Usage Guidelines3/5

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

'Send only what changes' is real guidance on how to call it (partial update, not full replace), which is the critical usage fact. However there is no explicit when-to-use-this-vs-alternatives guidance — nothing says to use track_product to create tracking or check_product to force an immediate check, so the agent must infer from sibling names.

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

Deploy Server