pricewatcha

Track product

track_product

Submit a public product URL for price tracking. Waits up to ~25s server-side; fast shops return status "completed" with product in one call. Slow jobs return status "running" with job_id — poll get_job_status. On failure, returns a structured error object with fields error.code, error.message, error.http_status, error.retry_recommended, and error.retry_after_seconds.

Input Schema

Name	Required	Description
`url`	Yes	Public product page URL from a supported shop
`watch`	No	If true (API key required), enroll the product for continuous scheduler updates.
`api_key`	No	Optional API key (pwk_live_...). Required for watch/refresh.
`refresh`	No	If true (API key required), force a re-scrape even if the URL is already in the catalog.

Output Schema

Name	Required	Description	Default
`hint`	No
`error`	No
`job_id`	Yes
`status`	Yes
`product`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 27, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```

changedOutput schema / properties / error / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {
-      "code": {
-        "type": "string"
-      },
-      "http_status": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "message": {
-        "type": "string"
-      },
-      "retry_after_seconds": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "retry_recommended": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "code",
-      "message",
-      "retry_recommended"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "code": {
+        "type": "string"
+      },
+      "http_status": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "message": {
+        "type": "string"
+      },
+      "retry_after_seconds": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "retry_recommended": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "code",
+      "message",
+      "retry_recommended"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / product / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {
-      "currency": {
-        "type": "string"
-      },
-      "current_price": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "last_checked_at": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "name": {
-        "type": "string"
-      },
-      "product_id": {
-        "type": "string"
-      },
-      "product_url": {
-        "type": "string"
-      },
-      "shop": {
-        "type": "string"
-      },
-      "status": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "product_id",
-      "name",
-      "shop",
-      "currency"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "currency": {
+        "type": "string"
+      },
+      "current_price": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "last_checked_at": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "name": {
+        "type": "string"
+      },
+      "product_id": {
+        "type": "string"
+      },
+      "product_url": {
+        "type": "string"
+      },
+      "shop": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "product_id",
+      "name",
+      "shop",
+      "currency"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed3 schema fields changedSep 7, 2026

addedInput schema / properties / api_key

Added value: +{
+  "description": "Optional API key (pwk_live_...). Required for watch/refresh.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / refresh

Added value: +{
+  "description": "If true (API key required), force a re-scrape even if the URL is already in the catalog.",
+  "type": "boolean"
+}

addedInput schema / properties / watch

Added value: +{
+  "description": "If true (API key required), enroll the product for continuous scheduler updates.",
+  "type": "boolean"
+}

First observedJun 7, 2026

TDQS

A4/5.0

Behavior5/5

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

Adds substantial context beyond annotations: the ~25s server-side blocking wait, the two possible terminal statuses and what each means, the polling follow-up, and the exact error object shape including retry_recommended and retry_after_seconds. Annotations cover only safety flags, so this description carries behavior disclosure well.

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?

Three tight sentences, front-loaded with the action, then the outcome branches, then failure shape. No filler and every clause conveys actionable information.

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?

An output schema exists, so return-shape explanation is technically redundant, though describing status values is still helpful. The only real gap is that the description never touches the watch/refresh enrollment behavior, leaving that entirely to the schema.

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 url, watch, api_key, and refresh are all documented in the schema. The description adds no additional meaning about their semantics — notably it never mentions watch/refresh or the API key requirement they imply. Baseline 3 is appropriate.

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?

Specific verb and resource: "Submit a public product URL for price tracking." It also distinguishes its async flow by naming get_job_status. However, it does not differentiate itself from the closely related sibling watch_product, which an agent could reasonably confuse for tracking enrollment.

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?

The description clearly routes the agent forward in the workflow (fast shops → completed, slow jobs → poll get_job_status), which is genuinely useful usage guidance. But it gives no guidance on when to choose this tool over siblings like watch_product, get_product, or search_products.

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

All pricewatcha tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.