Skip to main content
Glama
voriq-ai

smartleadai-mcp

by voriq-ai

SmartProspect: save a search filter

smartprospect_save_search

Save a named SmartProspect search filter for later reuse without running the search or consuming credits.

Instructions

Save a named SmartProspect search filter for later reuse. Safety — read-only: no; may consume SmartProspect credits: no; creates or modifies remote state: yes; can send email: no; destructive: no. Endpoint: POST https://prospect-api.smartlead.ai/api/v1/search-email-leads/search-filters/save-search. Creates remote state. Does not run the search and does not consume credits. Blocked in readonly mode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCities (max 2000 items).
nameNoFull names (max 2000 items).
levelNoSeniority levels (max 2000 items).
limitNoResult limit stored with the filter (1-10000).
stateNoStates (max 2000 items).
titleNoJob titles (max 2000 items).
countryNoCountries (max 2000 items).
lastNameNoLast names (max 2000 items).
firstNameNoFirst names (max 2000 items).
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).
search_stringYesHuman-readable name for the saved search.
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).
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 explicitly discloses safety-relevant behaviors beyond the annotations: it creates remote state, does not consume SmartProspect credits, cannot send email, is not destructive, and is blocked in readonly mode. It also provides the exact endpoint. This is highly transparent and goes well beyond the readOnlyHint/destructiveHint flags.

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 compact and well-structured, but there is some redundancy: the safety line states 'creates or modifies remote state: yes' and 'may consume SmartProspect credits: no,' and the next sentence repeats 'Creates remote state' and 'does not consume credits.' This duplication prevents a perfect conciseness 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?

For a tool with 28 parameters, the schema fully documents the parameters and the output schema exists. The description covers the key operational context: side effects, credit consumption, readonly behavior, and the endpoint. It does not explain the relationship to list/update saved searches, but this is not essential for invocation and sibling tool names provide that context.

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 input schema has 100% description coverage for all 28 parameters, including clear descriptions of each filter field and the required search_string. The description adds little beyond the word 'named,' so the schema carries the parameter semantics. The baseline of 3 applies because no compensation is needed.

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 starts with a clear action: 'Save a named SmartProspect search filter for later reuse.' This uses a specific verb and resource, and it distinguishes the tool from sibling tools like smartprospect_search_contacts (which runs a search) and smartprospect_update_saved_search (which modifies an existing filter).

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 practical usage context: it states the tool only saves the filter, 'Does not run the search and does not consume credits,' and is 'Blocked in readonly mode.' This helps an agent choose when to use it, though it does not explicitly name alternatives or exclusions relative to sibling tools.

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