Skip to main content
Glama
voriq-ai

smartleadai-mcp

by voriq-ai

SmartProspect: search contacts

smartprospect_search_contacts
Read-only

Find qualified leads by searching the SmartProspect database using filters like title, location, and company. Get a preview page with filter_id and scroll_id for paginated retrieval.

Instructions

Search the SmartProspect contact database with filters and return a preview page plus filter_id, total_count and scroll_id. Safety — read-only: yes; may consume SmartProspect credits: no; creates or modifies remote state: no; can send email: no; destructive: no. Endpoint: POST https://prospect-api.smartlead.ai/api/v1/search-email-leads/search-contacts. Read-only. Running a search does not fetch or reveal credit-gated contacts and does not spend credits by itself. limit is required and must be 1-500; every array filter accepts at most 2000 items. Pass the returned scroll_id back in to page through results; keep the filter_id to fetch or retrieve contacts later.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCities (max 2000 items).
nameNoFull names (max 2000 items).
levelNoSeniority levels (max 2000 items).
limitYesNumber of contacts to return (1-500). Required by Smartlead.
stateNoStates (max 2000 items).
titleNoJob titles (max 2000 items).
countryNoCountries (max 2000 items).
lastNameNoLast names (max 2000 items).
firstNameNoFirst names (max 2000 items).
scroll_idNoScroll ID returned by a previous search, to fetch the next page.
departmentNoDepartments (max 2000 items).
companyNameNoCompany names (max 2000 items).
excludeTitleNoJob titles to exclude (max 2000 items).
includeTitleNoJob titles to include (max 2000 items).
companyDomainNoCompany domains (max 2000 items).
companyKeywordNoCompany keywords (max 2000 items).
companyRevenueNoCompany revenue ranges (max 2000 items).
excludeCompanyNoCompanies to exclude (max 2000 items).
includeCompanyNoCompanies to include (max 2000 items).
companyIndustryNoIndustries (max 2000 items).
titleExactMatchNoMatch job titles exactly.
companyHeadCountNoCompany head count ranges (max 2000 items).
companyExactMatchNoMatch company names exactly.
companySubIndustryNoSub-industries (max 2000 items).
excludeCompanyDomainNoCompany domains to exclude (max 2000 items).
includeCompanyDomainNoCompany domains to include (max 2000 items).
include_full_recordsNoReturn complete preview records including names and personal fields. Defaults to false for privacy; opt in explicitly when those fields are needed.
companyDomainExactMatchNoMatch company domains exactly.
dontDisplayOwnedContactNoExclude contacts you already own.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
dataYes
errorNo
warningsYes
operationYes
paginationYes
credit_spendingYes
remote_mutationYes
Install Server

TDQS

A4.3/5.0
Behavior5/5

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

The description goes beyond the annotations by explicitly detailing safety semantics: 'may consume SmartProspect credits: no; creates or modifies remote state: no; can send email: no; destructive: no.' It also adds crucial behavioral context that 'Running a search does not fetch or reveal credit-gated contacts and does not spend credits by itself.' This clarifies the tool's side effects and limitations, adding value beyond the readOnlyHint/openWorldHint annotations. No contradictions with annotations.

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 description is structured with a clear opening sentence followed by safety details, endpoint, and usage notes. It is relatively concise but includes some redundancy: the safety list already states read-only, and then it is repeated ('Read-only.'). The endpoint URL is useful but not essential for an agent. Overall, it is efficient and front-loaded, but a few redundant phrases prevent a perfect score.

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 the tool's complexity (29 parameters, output schema present), the description provides sufficient context for initial use. It explains the tool's purpose, safety profile, pagination, and how to use filter_id for later steps (implying a workflow). The output schema covers return values, so not explaining them is acceptable. However, it does not clarify the distinction between preview records and full records beyond the include_full_records parameter, which might be a slight gap.

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?

The schema description coverage is 100%, with every parameter documented. The description adds little beyond the schema: it reiterates that limit is required (1-500) and array filters have max 2000 items, which is already in the schema. It does clarify the scroll_id parameter's use ('Pass the returned scroll_id back in to page through results'), but the schema describes it similarly. Thus, the description does not significantly enhance parameter 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 the tool's purpose: 'Search the SmartProspect contact database with filters and return a preview page plus filter_id, total_count and scroll_id.' This uses a specific verb ('search') and resource ('contact database'), and distinguishes it from sibling tools like get_contacts or fetch_contacts, which retrieve full records. The mention of returning a preview page and pagination identifiers clarifies the tool's unique role.

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 provides clear context on when to use this tool: it is safe for initial searches (does not spend credits or reveal credit-gated contacts) and explains how to paginate with scroll_id and use filter_id for later retrieval. However, it does not explicitly state alternatives or when *not* to use the tool, though the pagination and filter_id guidance implicitly directs users to other tools (like fetch_contacts) for full data.

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

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/voriq-ai/smartlead-mcp'

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