Skip to main content
Glama
enzoemir1

leadpipe-mcp

Search Leads

lead_search
Read-onlyIdempotent

Search and filter the lead pipeline by free-text query, status, score range, source, tags, and date. Get paginated results with total count for exports, scoring, and dashboards.

Instructions

Search and filter the lead pipeline. Optional filters: query (free-text over name/email/company), status ("new"|"qualified"|"disqualified"|"contacted"|"converted"), min_score, max_score, source, tags (array), date_from/date_to. Pagination via limit (default 50, max 200) and offset. Returns {total, leads[]}. Use this to drive exports, targeted scoring, and dashboards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoCase-insensitive substring search over email, first_name, last_name, job_title, and company.name. AND-combined with the other filters.
statusNoRestrict to a single status: new (just ingested), enriched (lead_enrich done), scored (has score), qualified (score ≥ threshold), disqualified, exported, archived.
min_scoreNoInclusive lower bound on score (0–100). Combine with status="qualified" for high-priority follow-up lists.
max_scoreNoInclusive upper bound on score (0–100). Useful for review queues — e.g. min_score=40, max_score=60 to surface borderline leads.
sourceNoFilter to a single source channel.
tagsNoTags that must ALL be present on the lead (AND semantics). Empty array is ignored.
limitNoPage size, 1–100. Defaults to 20.
offsetNoNumber of results to skip for pagination. Defaults to 0.
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating a safe, read-only operation. The description adds that it returns {total, leads[]} and mentions API behavior but doesn't contradict annotations.

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?

The description is concise (4 sentences), front-loaded with purpose, then lists filters, pagination, return format, and use cases. No wasted words.

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?

Given 8 optional parameters and no output schema, the description covers all filters, pagination, return shape, and primary use cases. It lacks explanation of status field semantics but the schema's enum descriptions compensate.

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?

Input schema describes all 8 parameters with 100% coverage. The description adds value by explaining AND-combined filters and providing usage examples like 'min_score=40, max_score=60 for borderline leads', which improves understanding beyond the schema.

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?

The description clearly states 'Search and filter the lead pipeline' and lists specific use cases like exports and dashboards, distinguishing it from sibling tools such as lead_ingest, lead_qualify, and lead_score.

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?

The description suggests when to use the tool ('drive exports, targeted scoring, and dashboards') but does not explicitly state when not to use it or name alternative tools. However, the context of siblings implies differentiation.

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/enzoemir1/leadpipe-mcp'

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