Skip to main content
Glama

LeadMarina

Get search results

get_search_results
Read-only

Fetch a search's leads with verification filled in as enrichment progresses. Poll until enrichment is 'complete'. Each lead includes verified emails (SMTP status), verified phones (line type + carrier), owner name where identified, socials, and the business profile.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "search_id": "<search_id>"
    },
    "name": "get_search_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax leads to return (default 25, max 1000).
offsetNoPagination offset (default 0).
search_idYesThe search_id returned by search_leads or enrich_domains.

Output Schema

NameRequiredDescriptionDefault
queryNo
stageNoqueued | discovering | enriching | verifying | complete | failed | cancelled. 'verifying' means every row is delivered and contacts are being verified — often the longest phase, not a stall.
periodNoOn a rate-limited plan: { limit, used, resets_at }. Null on a metered plan — and when the period's usage couldn't be read (leads_remaining is null too).
resultsYes
showingNoRange shown, e.g. '1–25'.
locationNo
progressNo{ done, total } rows enriched so far.
search_idYes
enrichmentYes'pending' or 'complete'.
next_offsetNoPass as offset to fetch the next page; null on the last page.
total_leadsYes
data_sourcesNoWhere 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.
queue_positionNoFor queued searches, the place in this account's own queue (1 = next).
leads_remainingNoLeads spendable now. On a plan with no monthly quota this is what is left in the current 7-day period, not a monthly balance. Null when that period's usage couldn't be read just then — ask again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / leads_remaining / description
      Previous value: -"Leads spendable now. On a plan with no monthly quota this is what is left in the current 7-day period, not a monthly balance."New value: +"Leads spendable now. On a plan with no monthly quota this is what is left in the current 7-day period, not a monthly balance. Null when that period's usage couldn't be read just then — ask again."
    • changedOutput schema / properties / period / description
      Previous value: -"On a rate-limited plan: { limit, used, resets_at }. Null on a metered plan."New value: +"On a rate-limited plan: { limit, used, resets_at }. Null on a metered plan — and when the period's usage couldn't be read (leads_remaining is null too)."
  2. Changed2 schema fields changed
    • addedOutput schema / properties / results / items / properties / country
      Added value: +{
      +  "description": "ISO 3166 alpha-2 (\"US\", \"GB\").",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / results / items / properties / postal_code
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  3. Changed3 schema fields changed
    • 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"
      +  ]
      +}
  4. Changed1 schema field changed
    • 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"
      +}
  5. Changed9 schema fields changed
    • addedOutput schema / properties / results / items / properties / address
      Added value: +{
      +  "description": "Street address from the Google listing.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / results / items / properties / claimed
      Added value: +{
      +  "description": "Whether the owner has claimed the Google listing.",
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / results / items / properties / email_status
      Added value: +{
      +  "description": "Email 1's SMTP verdict: safe | risky | invalid | unknown.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / results / items / properties / google_cid
      Added value: +{
      +  "description": "Google listing id (the query_leads google_cid field).",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / results / items / properties / maps_url
      Added value: +{
      +  "description": "The Google Maps link for the listing.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / results / items / properties / phone
      Added value: +{
      +  "description": "The Google Maps number.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / results / items / properties / phone_line_type
      Added value: +{
      +  "description": "Phone 1's line type: mobile, fixed_line, voip or toll_free usually; also unknown, fixed_line_or_mobile and the other values query_leads lists.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / results / items / properties / primary_email
      Added value: +{
      +  "description": "Email 1: the first address in emails_data, the one email_status describes. Before emails are verified, the lead's primary address.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / results / items / properties / primary_phone
      Added value: +{
      +  "description": "Phone 1: the first number in phones_data, the one phone_line_type describes. Before phones are verified, the lead's primary number, or its Google Maps number.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  6. Changed2 schema fields changed
    • 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, not a monthly balance."
    • addedOutput schema / properties / period
      Added value: +{
      +  "description": "On a rate-limited plan: { limit, used, resets_at }. Null on a metered plan.",
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
  7. Changed1 schema field changed
    • addedOutput schema / properties / next_offset
      Added value: +{
      +  "description": "Pass as offset to fetch the next page; null on the last page.",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
  8. Changed3 schema fields changed
    • addedOutput schema / properties / progress
      Added value: +{
      +  "description": "{ done, total } rows enriched so far.",
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / queue_position
      Added value: +{
      +  "description": "For queued searches, the place in this account's own queue (1 = next).",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / stage
      Added value: +{
      +  "description": "queued | discovering | enriching | verifying | complete | failed | cancelled. 'verifying' means every row is delivered and contacts are being verified — often the longest phase, not a stall.",
      +  "type": "string"
      +}
  9. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max leads to return (default 25, max 100)."New value: +"Max leads to return (default 25, max 1000)."
  10. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, and the description adds the key trait annotations cannot convey: results are progressively enriched and may be incomplete until status reaches 'complete'. It does not discuss rate limits or pagination behavior beyond the schema.

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?

Three short sentences, front-loaded with the action and the polling instruction. The final lead-field inventory partially restates what the output schema already declares, which is the main piece of mild redundancy.

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?

With an output schema present, return shape need not be explained, and the description nonetheless summarizes the enrichment lifecycle an agent needs to poll correctly. Combined with full schema coverage and safety annotations, an agent has enough to invoke it correctly, though the 'complete' status source is not described.

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%, with limit, offset, and search_id each documented, so the schema carries the semantic load. The description adds no additional meaning about limits, offsets, or the search_id format, which is acceptable at this coverage level but is a baseline performance.

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?

Uses a specific verb ('Fetch') plus a precise resource ('a search's leads') and scopes the result set to leads belonging to one search_id, which separates it from query_leads and search_leads. It never names a sibling explicitly, so differentiation is implied rather than stated.

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

Usage Guidelines4/5

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

'Poll until enrichment is complete' is concrete operational guidance, and the schema identifies search_id as coming from search_leads or enrich_domains, making the call sequence clear. It still lacks an explicit statement of when NOT to use it (e.g., for fresh un-enriched results) or a named alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.