Skip to main content
Glama

maps_leads

Find qualified sales leads on Google Maps filtered by Lead Quality Score. Build targeted outreach lists by specifying industry, location, and minimum score.

Instructions

Find qualified sales leads on Google Maps filtered by Lead Quality Score. Best for building targeted outreach lists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
industryYesIndustry or business type, e.g. 'restaurants'
locationYesCity or area, e.g. 'Miami FL'
min_scoreNoMinimum Lead Quality Score threshold (default: 60)
google_keyYesYour Google Places API key

Implementation Reference

  • Tool registration in ListToolsRequestSchema: defines the 'maps_leads' tool name, description, and input schema with industry, location, min_score, and google_key properties.
        {
          name: "maps_leads",
          description:
            "Find qualified sales leads on Google Maps filtered by Lead Quality Score. Best for building targeted outreach lists.",
          inputSchema: {
            type: "object",
            properties: {
              industry: {
                type: "string",
                description: "Industry or business type, e.g. 'restaurants'",
              },
              location: {
                type: "string",
                description: "City or area, e.g. 'Miami FL'",
              },
              min_score: {
                type: "number",
                description: "Minimum Lead Quality Score threshold (default: 60)",
              },
              google_key: {
                type: "string",
                description: "Your Google Places API key",
              },
            },
            required: ["industry", "location", "google_key"],
          },
        },
      ],
    }));
  • Handler dispatch in the CallToolRequestSchema switch: extracts industry, location, min_score, google_key from args and calls findSalesLeads().
    case "maps_leads": {
      const { industry, location, min_score, google_key } = args as {
        industry: string;
        location: string;
        min_score?: number;
        google_key: string;
      };
      result = await findSalesLeads(industry, location, google_key, min_score);
      break;
    }
  • Core implementation of findSalesLeads: searches maps businesses for the given industry/location, filters by lead quality score (default 60), and returns qualified leads with metadata.
    export async function findSalesLeads(
      industry: string,
      location: string,
      apiKey: string,
      minScore = 60
    ): Promise<MapsLeadsResult> {
      const result = await searchMapsBusinesses(industry, location, apiKey, 60);
    
      const qualified = result.businesses.filter(
        (b) => b.lead_quality_score >= minScore
      );
    
      return {
        industry,
        location,
        min_score: minScore,
        total_qualified: qualified.length,
        leads: qualified,
        searched_at: new Date().toISOString(),
      };
    }
  • Type schema for the MapsLeadsResult return value, containing industry, location, min_score, total_qualified, leads array, and timestamp.
    export interface MapsLeadsResult {
      industry: string;
      location: string;
      min_score: number;
      total_qualified: number;
      leads: PlaceBusiness[];
      searched_at: string;
    }
  • src/mcp-stdio.ts:22-22 (registration)
    Import of the findSalesLeads function from the maps tools module, which is the actual implementation of the maps_leads tool.
    import { searchMapsBusinesses, findSalesLeads } from "./tools/maps.js";
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose whether the operation is read-only, any authentication requirements beyond the API key, or behavior when no leads are found. The description is minimal on behavioral context.

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?

Two sentences, no filler, front-loaded purpose. Every word adds value.

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

Completeness2/5

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

No output schema and no annotations. The description does not explain the concept of Lead Quality Score, output format, or what happens if no leads match. For a tool with 4 parameters and no structured metadata, more context is needed.

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?

Input schema has 100% coverage, so baseline is 3. The description mentions 'Lead Quality Score' but does not add details beyond schema (e.g., what min_score represents or how it's calculated). No additional parameter meaning given.

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?

Description clearly states the tool finds qualified sales leads on Google Maps filtered by Lead Quality Score, distinguishing it from the sibling 'maps_search' which is likely a general search. The purpose is specific and actionable.

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

Usage Guidelines3/5

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

Says 'Best for building targeted outreach lists,' which implies a use case but does not explicitly state when to use or avoid this tool, nor compare to sibling tools like 'maps_search'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/samrothschild23/intelligence-api'

If you have feedback or need assistance with the MCP directory API, please join our Discord server