Skip to main content
Glama
Sign In
LeadIntel

LeadIntel

by rushikesheleven
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

export_leads

Search businesses by query, location, or category, then save results as Excel, CSV, or JSON files for outreach and analysis.

Instructions

    Search for businesses and export results to an Excel (.xlsx), CSV, or JSON file.

    Features:
    - Excel: Creates a multi-sheet workbook with frozen headers, auto-filters, and clean styling.
    - CSV: Standard tabular spreadsheet export.
    - JSON: Complete structured lead metadata with timestamps and attribution.

    Args:
        query: Free-text search term (e.g. 'cafe', 'software').
        location: City, region, or coordinates.
        category: Industry or category filter.
        limit: Max number of leads to export (1-200, default 50).
        format: 'excel' (or 'xlsx'), 'csv' (default), or 'json'.
        output_path: Destination file path (optional).

    Returns:
        Dict containing output_path, row_count, format, and data attribution.

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
formatNocsv
categoryNo
locationNo
output_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the return dict keys (output_path, row_count, format, attribution) and what each format physically produces, but it never states where files land when output_path is omitted, whether existing files are overwritten, or that this tool writes to disk at all.

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?

The opening sentence is front-loaded and the format bullets are genuinely informative about output differences. The Args block duplicates schema field names, but each entry adds at least one detail (ranges, aliases), so little of it is pure repetition.

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?

For a six-parameter tool with no annotations and no output schema, the definition covers purpose, all parameters, and the shape of the return value. What is missing is side-effect detail — default write location and overwrite behavior — which matters for a tool that produces files.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it largely does: every one of the six parameters is explained, the 1-200 limit range and default 50 are added beyond the bare schema, and the 'excel'/'xlsx' alias plus default 'csv' are clarified. Remaining gap is output_path, described only as 'optional' with no default-location or overwrite semantics.

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?

The description states a specific pair of actions (search businesses, export results) and the concrete artifact produced (xlsx/csv/json file), which an agent can grasp immediately. It does not explicitly distinguish itself from the sibling search_businesses, leaving the boundary between 'search and view' and 'search and export' implicit.

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?

Usage is implied by the word 'export' and the format list, so an agent can infer this is the tool for producing files. However, there is no explicit when-to-use statement, no mention that search_businesses should be preferred for interactive lookups, and no guidance on choosing between formats beyond a one-word gloss.

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

Deploy Server

Other Tools