HirePulse MCP

Batch Company Lookup

batch_lookup

Read-only

Run one data lookup—tech stack, open jobs, hiring intent, Google Ads, or company profile—across up to 50 domains, with a free quote and pay only for rows with data.

Instructions

Runs one tool (tech stack, open jobs, hiring intent, Google Ads or company profile) on up to 50 domains. Step 1 is a free check that returns a quote_id priced only for rows with data; step 2 pays that exact amount, at most $1.00. Rows without data are free. Use for the same lookup across several known domains; use get_company_profile for one domain or find_hot_buyers to rank hiring signals. A quote does not authorize payment.

Input Schema

Name	Required	Description
`tool`	No	Data tool to run for each domain during quote creation; omit when redeeming a quote_id.
`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.
`domains`	No	Public company domains without a URL scheme, path or port.
`quote_id`	No	quote_id from step 1. Send it alone to pay and receive the results.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 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"
+}

addedInput schema / properties / tool / description

Added value: +"Data tool to run for each domain during quote creation; omit when redeeming a quote_id."

addedOutput schema / anyOf

Added value: +[
+  {
+    "properties": {
+      "billable_count": {
+        "type": "integer"
+      },
+      "cold": {
+        "description": "hot-buyers: domains below the threshold, free.",
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "expires_at": {
+        "format": "date-time",
+        "type": "string"
+      },
+      "next": {
+        "type": "string"
+      },
+      "price_micro_usd": {
+        "type": "integer"
+      },
+      "price_usd": {
+        "type": "number"
+      },
+      "quote_id": {
+        "type": "string"
+      },
+      "results": {
+        "description": "Paid rows, after step 2.",
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "status": {
+        "description": "quote: pay with quote_id to get the results. nothing_billable: no charge. ok: paid results.",
+        "enum": [
+          "quote",
+          "nothing_billable",
+          "ok"
+        ],
+        "type": "string"
+      },
+      "statuses": {
+        "description": "Status of every domain, free.",
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "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 / properties

Removed value: -{
-  "billable_count": {
-    "type": "integer"
-  },
-  "cold": {
-    "description": "hot-buyers: domains below the threshold, free.",
-    "items": {
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "expires_at": {
-    "format": "date-time",
-    "type": "string"
-  },
-  "next": {
-    "type": "string"
-  },
-  "price_micro_usd": {
-    "type": "integer"
-  },
-  "price_usd": {
-    "type": "number"
-  },
-  "quote_id": {
-    "type": "string"
-  },
-  "results": {
-    "description": "Paid rows, after step 2.",
-    "items": {
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "status": {
-    "description": "quote: pay with quote_id to get the results. nothing_billable: no charge. ok: paid results.",
-    "enum": [
-      "quote",
-      "nothing_billable",
-      "ok"
-    ],
-    "type": "string"
-  },
-  "statuses": {
-    "description": "Status of every domain, free.",
-    "items": {
-      "type": "object"
-    },
-    "type": "array"
-  }
-}

removedOutput schema / required
```
Removed value: -[
-  "status"
-]
```

First observedv0.1.0Oct 21, 2026

TDQS

A3.9/5.0

Behavior1/5

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

The description says step 2 'pays that exact amount' and that 'A quote does not authorize payment,' which describes a monetary transaction. This directly contradicts the readOnlyHint=true annotation, which asserts the tool has no side effects. Despite otherwise useful disclosure about free checks and pricing caps, the contradiction is a critical inconsistency.

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?

The description is front-loaded with the core action and domain limit, then follows with pricing details and alternatives in a logical sequence. Every sentence adds distinct information without redundancy, and the closing warning about quotes is a useful reminder.

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?

Given the output schema exists (so return values need not be explained) and the annotations (readOnlyHint, openWorldHint), the description covers all necessary aspects for correct invocation: tool selection, domain limits, the two-step quote/payment process, pricing rules, and explicit alternatives. Nothing essential for calling the tool is missing.

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 parameter meanings are fully documented in the input schema (e.g., tool enum, domains format, quote_id usage). The description adds context about the two-step flow and the 'at most $1.00' price cap, but does not meaningfully extend the semantic definition of any parameter beyond what the schema already provides.

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?

The description states a specific action (runs one tool on up to 50 domains) and enumerates the available tools, making the scope immediately clear. It also explicitly names sibling tools for alternative use cases, so an agent can distinguish this tool from get_company_profile and find_hot_buyers without opening schemas.

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?

It specifies when to use this tool (same lookup across several known domains) and names two explicit alternatives with their respective conditions (get_company_profile for one domain, find_hot_buyers for ranking hiring signals). The two-step quote/payment flow is also clearly described as part of the usage pattern.

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