HirePulse MCP

Conversion Leak Finder

muse_conversion_leak_lead_finder

Read-only

Identifies conversion leak leads by qualifying a known store for outreach based on schema gaps and Google ad activity, returning structured public evidence and explicit unknowns.

Instructions

Returns structured public evidence and explicit unknowns. Store check for schema gaps, Google ad activity and public business contacts; a lead qualifies only with ad and SEO evidence. Public emails are not verified decision makers. $0.05 per qualified result. Use to qualify a known store for outreach about schema gaps; use muse_agentic_store_readiness_auditor for an audit without lead qualification or extract_company_contacts for contacts only. Does not send outreach or measure conversion loss.

Input Schema

Name	Required	Description	Default
`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.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 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"
+]

addedOutput schema / anyOf

Added value: +[
+  {
+    "description": "Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null.",
+    "properties": {
+      "active_ad_spend_verified": {
+        "type": [
+          "boolean",
+          "null"
+        ]
+      },
+      "candidate": {
+        "type": "boolean"
+      },
+      "decision_maker_verified": {
+        "type": "boolean"
+      },
+      "domain": {
+        "type": "string"
+      },
+      "error_reason": {
+        "type": "string"
+      },
+      "limitations": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "public_contacts": {
+        "type": "object"
+      },
+      "readiness": {
+        "type": "object"
+      },
+      "seo_traffic_verified": {
+        "type": [
+          "boolean",
+          "null"
+        ]
+      },
+      "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_ad_spend_verified": {
-    "type": [
-      "boolean",
-      "null"
-    ]
-  },
-  "candidate": {
-    "type": "boolean"
-  },
-  "decision_maker_verified": {
-    "type": "boolean"
-  },
-  "domain": {
-    "type": "string"
-  },
-  "error_reason": {
-    "type": "string"
-  },
-  "limitations": {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "public_contacts": {
-    "type": "object"
-  },
-  "readiness": {
-    "type": "object"
-  },
-  "seo_traffic_verified": {
-    "type": [
-      "boolean",
-      "null"
-    ]
-  },
-  "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 only cover readOnly and openWorld, but the description adds substantive behavior: pricing at $0.05 per qualified result, the qualification gate, the evidence-vs-unknowns output posture, and the caveat that public emails are not verified decision makers. That caveat is exactly the kind of risk context annotations cannot carry.

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?

Dense and largely front-loaded, with qualification criteria and pricing stated early. The opener 'Returns structured public evidence and explicit unknowns' is abstract and slightly awkward, but every remaining sentence carries real information.

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?

An output schema exists, so return shape need not be explained; the description supplies what the schema cannot – qualification criteria, cost, evidence caveats, and exclusions. An agent has everything needed to decide and call correctly.

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 both the domain format and the optional context field are already documented. The description implies the input is a known store domain but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 resource (a known store) and a specific output (public evidence of schema gaps, Google ad activity, contacts) with an explicit qualification rule: a lead qualifies only with ad and SEO evidence. It is easily distinguished from siblings like muse_agentic_store_readiness_auditor and extract_company_contacts, which are named directly.

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?

Explicit 'use to qualify a known store for outreach about schema gaps' plus two named alternatives with the conditions that select them (audit without lead qualification; contacts only). It also states a negative scope – does not send outreach or measure conversion loss – closing the obvious misuse paths.

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