leadmarina

Search local-business leads

search_leads

Run a live search for local businesses by niche + city (e.g. query 'electrician', location 'Austin, TX'). Returns a search_id and, usually, the first batch immediately (its listings are in results; their emails and phones are not verified yet — when discovery is 'in_progress' the provider was slow and the whole search was queued, so the leads arrive through get_search_results); more results are found and verified in the background — every email is SMTP-checked and phones are verified with line type + carrier. Spends 1 lead per result. Poll get_search_results until enrichment is 'complete'. If enrichment is already 'complete', nothing was found and nothing more is coming; if capped is true, the balance covered fewer leads than were found.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	Yes	Business niche/category keyword, e.g. 'electrician'.
`location`	No	City, e.g. 'Austin, TX'. Not needed with location_code, which is always what is searched.
`location_code`	No	Optional exact location code. When given, it is what is searched, whatever location says. Sent with location, the search is named after the code's own place (or after location when the code's own name cannot be looked up); sent alone, the search is unnamed and location comes back null.

Output Schema

TableJSON Schema

Name	Required	Description
`found`	No	Listings found in the first batch, before the balance capped delivery.
`query`	Yes
`capped`	No	True when the lead balance covered fewer leads than were found — relay this to the user.
`results`	No	The first batch, as delivered — contacts are verified in the background (get_search_results).
`location`	No	The place searched, as the location list names it (the location sent, when a code's own name could not be looked up); null for a location_code sent alone.
`discovery`	No	'complete', or 'in_progress' when the search was queued whole.
`next_step`	No
`search_id`	Yes
`enrichment`	Yes	'pending' until background verification finishes; 'complete' at once when nothing was found.
`data_sources`	No	Where the sources, licences and notices are for emails and owner names that may come from open datasets and public records. Pass it on with any of this data you share.
`leads_remaining`	No	Leads spendable now. On a plan with no monthly quota this is what is left in the current 7-day period.
`delivered_so_far`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 9, 2026

addedOutput schema / properties / results / items / properties / contact_name

Added value: +{
+  "description": "The person the business's own website names as running part of it (a manager, a practice's doctor) when it names no owner.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / results / items / properties / contact_title

Added value: +{
+  "description": "That person's role, as the website gives it.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / results / items / properties / people

Added value: +{
+  "description": "Everyone the business's own website names as working there, each { name, title, kind } (kind: owner, manager, practitioner, staff).",
+  "items": {
+    "type": "object"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

Changed1 schema field changedOct 8, 2026

addedOutput schema / properties / data_sources

Added value: +{
+  "description": "Where the sources, licences and notices are for emails and owner names that may come from open datasets and public records. Pass it on with any of this data you share.",
+  "type": "string"
+}

Changed8 schema fields changedOct 6, 2026

changedInput schema / properties / location / description

Previous value: -"City, e.g. 'Austin, TX'. Ignored if location_code is given."New value: +"City, e.g. 'Austin, TX'. Not needed with location_code, which is always what is searched."

changedInput schema / properties / location_code / description

Previous value: -"Optional exact location code (skips the city lookup)."New value: +"Optional exact location code. When given, it is what is searched, whatever location says. Sent with location, the search is named after the code's own place (or after location when the code's own name cannot be looked up); sent alone, the search is unnamed and location comes back null."

addedOutput schema / properties / capped

Added value: +{
+  "description": "True when the lead balance covered fewer leads than were found — relay this to the user.",
+  "type": "boolean"
+}

addedOutput schema / properties / discovery

Added value: +{
+  "description": "'complete', or 'in_progress' when the search was queued whole.",
+  "type": "string"
+}

changedOutput schema / properties / enrichment / description

Previous value: -"'pending' until background verification finishes."New value: +"'pending' until background verification finishes; 'complete' at once when nothing was found."

addedOutput schema / properties / found

Added value: +{
+  "description": "Listings found in the first batch, before the balance capped delivery.",
+  "type": "number"
+}

addedOutput schema / properties / location / description

Added value: +"The place searched, as the location list names it (the location sent, when a code's own name could not be looked up); null for a location_code sent alone."

addedOutput schema / properties / results

Added value: +{
+  "description": "The first batch, as delivered — contacts are verified in the background (get_search_results).",
+  "items": {
+    "properties": {
+      "category": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "city": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "emails_data": {
+        "description": "Verified emails with SMTP status."
+      },
+      "enrichment_status": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "owner_name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "phones_data": {
+        "description": "Verified phones with line type + carrier."
+      },
+      "rating": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "reviews": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "socials": {
+        "description": "Social profile links keyed by platform."
+      },
+      "state": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "website": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedSep 4, 2026

addedOutput schema / properties / leads_remaining / description

Added value: +"Leads spendable now. On a plan with no monthly quota this is what is left in the current 7-day period."

First observedJul 24, 2026

TDQS

Score is being calculated.

All leadmarina 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.

Resources

Need Help?