HirePulse MCP

Checkout Promo Codes

checkout_active_promo_code_finder

Read-only

Collect coupon code candidates from a shop's homepage metadata before checkout to identify possible discounts; codes are unverified and not applied.

Instructions

Returns structured public evidence and explicit unknowns. Coupon code candidates published in the homepage metadata of a shop, with the source text. Codes are not verified at checkout. $0.01 per non-empty result. Use to collect possible discounts before checkout; use universal_product_url_to_json for product prices and availability. Does not apply coupons or place an order.

Input Schema

Name	Required	Description
`domain`	Yes	Public domain without scheme, path or port.
`context`	No	Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.
`product_category`	No	Optional category context for the supplied store; does not guarantee category-specific or checkout-verified coupons.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv1.0.0Oct 27, 2026

addedInput schema / properties / context

Added value: +{
+  "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+  "type": "string"
+}

changedInput schema / properties / domain / examples

Previous value: -[
-  "example.com"
-]New value: +[
+  "allbirds.com"
+]

addedInput schema / properties / product_category / description

Added value: +"Optional category context for the supplied store; does not guarantee category-specific or checkout-verified coupons."

addedOutput schema / anyOf

Added value: +[
+  {
+    "description": "Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null.",
+    "properties": {
+      "active_codes": {
+        "items": {
+          "properties": {
+            "checkout_verified": {
+              "type": "boolean"
+            },
+            "code": {
+              "type": "string"
+            },
+            "confidence": {
+              "maximum": 1,
+              "minimum": 0,
+              "type": "number"
+            },
+            "discount_description": {
+              "type": "string"
+            },
+            "promo_landing_url": {
+              "type": "string"
+            },
+            "source": {
+              "enum": [
+                "seo_meta"
+              ],
+              "type": "string"
+            }
+          },
+          "required": [
+            "code",
+            "discount_description",
+            "source",
+            "promo_landing_url",
+            "confidence",
+            "checkout_verified"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "best_offer_summary": {
+        "type": "string"
+      },
+      "domain": {
+        "type": "string"
+      },
+      "error_reason": {
+        "type": "string"
+      },
+      "limitations": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "promos_found": {
+        "type": "boolean"
+      },
+      "sources_checked": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "status": {
+        "enum": [
+          "ok",
+          "no_data",
+          "unreachable"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "domain",
+      "status"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {
+      "code": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "status": {
+        "maximum": 599,
+        "minimum": 400,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "status",
+      "code"
+    ],
+    "type": "object"
+  }
+]

removedOutput schema / description

Removed value: -"Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null."

removedOutput schema / properties

Removed value: -{
-  "active_codes": {
-    "items": {
-      "properties": {
-        "checkout_verified": {
-          "type": "boolean"
-        },
-        "code": {
-          "type": "string"
-        },
-        "confidence": {
-          "maximum": 1,
-          "minimum": 0,
-          "type": "number"
-        },
-        "discount_description": {
-          "type": "string"
-        },
-        "promo_landing_url": {
-          "type": "string"
-        },
-        "source": {
-          "enum": [
-            "seo_meta"
-          ],
-          "type": "string"
-        }
-      },
-      "required": [
-        "code",
-        "discount_description",
-        "source",
-        "promo_landing_url",
-        "confidence",
-        "checkout_verified"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "best_offer_summary": {
-    "type": "string"
-  },
-  "domain": {
-    "type": "string"
-  },
-  "error_reason": {
-    "type": "string"
-  },
-  "limitations": {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "promos_found": {
-    "type": "boolean"
-  },
-  "sources_checked": {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "status": {
-    "enum": [
-      "ok",
-      "no_data",
-      "unreachable"
-    ],
-    "type": "string"
-  }
-}

removedOutput schema / required

Removed value: -[
-  "domain",
-  "status"
-]

First observedv0.1.0Oct 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover readOnly and openWorld, but the description adds substantive context beyond them: unverified-at-checkout caveat, source-text provenance, explicit unknowns, a $0.01 per non-empty result pricing model, and confirmation it does not mutate anything. These are exactly the traits an agent needs for cost/risk judgment.

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?

Every sentence earns its place: return type, provenance, verification caveat, pricing, usage routing, and exclusions. Slightly abstract opener ('structured public evidence and explicit unknowns') precedes the concrete statement, so it is not perfectly front-loaded but remains tight.

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

Completeness5/5

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

With an output schema available, the description need not explain return structure; it fills the remaining gaps an agent needs — provenance, non-verification, cost, and non-mutation — making the definition complete for correct invocation.

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 the domain/context/product_category semantics are already fully documented in the schema. The description adds no syntax or format detail beyond it, which matches the baseline 3 when the schema does the heavy lifting.

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

Purpose5/5

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

States a specific verb and resource: returns coupon code candidates published in a shop's homepage metadata, along with source text. It explicitly distinguishes itself from the sibling universal_product_url_to_json and clarifies that codes are not checkout-verified, so the agent can tell what kind of artifact it gets.

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

Usage Guidelines5/5

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

Names the use case ('collect possible discounts before checkout'), the alternative for a different need (universal_product_url_to_json for prices and availability), and the exclusions ('does not apply coupons or place an order'). Both when-to-use and when-not-to-use are explicit.

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