Skip to main content
Glama

Reveal contact details

argorant_reveal_people
Destructive

Reveal the full contact details (name, job, company, work email and profile link) of a small group of people who match a search. Use it only for the few people the user wants now, after they approved the cost. For a file of many people use argorant_create_export, and for one known person use argorant_enrich or argorant_find_email. Only working email addresses are shown and charged, at 1 credit for each person whose email is new to this account. People this account already unlocked are free, in the app, the API and here. Ask the user before you spend credits. Phone numbers are only included when include_phones is true. They cost 10 credits per phone number returned, nothing if none is found. Ask the user before spending. A daily safety limit caps how many people can be revealed. It takes the same filters as argorant_count_people. The answer's summary says what was shown and what it cost; tell the user. More in the docs at https://docs.argorant.com/docs/agents/tools#reveal-enrich-export

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "argorant_reveal_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFree text for the search, such as "dental clinics" or a person's job and place. A request such as "software companies selling to restaurants" is read as company_category and sells_to. Prefer the dedicated filters when you know them.
cityNoCities by name. A comma means any of them.
limitNoHow many people to reveal (default 10). Keep it to the people the user asked for.
stateNoStates or provinces by name or code, such as Texas or TX. A comma means any of them.
titleNoJob titles to find. A comma means any of them. Short forms work both ways, so CFO also finds Chief Financial Officer.
genderNoGender, female or male, based on first name and country. Names used for both women and men are left out. Not available for lending audiences.
radiusNoDistance around the place, between 0.5 and 500.
countryNoCountries, or regions such as Europe, EMEA, DACH, Nordics, Benelux, APAC, LATAM, North America or GCC. A comma means any of them. Regions can overlap. Egypt is in both Middle East and Africa, Mexico is in both North America and LATAM, and Turkey counts as Middle East, not Europe. A person is counted once, even when several of the regions you name include their country.
industryNoIndustries by name, such as Software or Hospitals and Health Care. A comma means any of them.
keywordsNoWords that describe what the company does, such as fintech, MSP or freight forwarding. A comma means any of them. They match the company's name, tags, industry and description, not people's own skills, unless you set where keywords look to people or any.
near_latNoLatitude of the place to search around. Use it with near_lon and radius.
near_lonNoLongitude of the place to search around. Use it with near_lat and radius.
sells_toNoWho the company sells to, used with company_category. One of restaurants, construction, dentists, salons, auto_repair, hotels, logistics, trades, retailers or smb. It finds the companies that sell, never their customers.
geographyNoThe same as country. Countries or regions such as Europe, DACH, Nordics or North America.
has_phoneNotrue keeps only people with a phone number on file. Phone numbers themselves are only shown when paid for.
seniorityNoHow senior the person is. Pick one or more.
near_placeNoA place to search around, written out as a city or a postal code, for example Denver, Colorado or 10115 Berlin. Use it with radius.
departmentsNoThe person's department. Pick one or more.
founded_maxNoCompanies founded in this year or earlier, such as 2020.
founded_minNoCompanies founded in this year or later, such as 2015. Companies whose founding year is not known are left out.
radius_unitNoUnit of the distance, miles (mi, the default) or kilometers (km).
revenue_maxNoLargest yearly revenue in US dollars, such as 50M.
revenue_minNoSmallest yearly revenue in US dollars, such as 1M. A company counts when its revenue range overlaps yours.
title_matchNoHow a job title must match. words (the default) needs every word as a whole word, so Data does not match Database. exact needs the whole title to be one of the values, so CEO does not match Founder & CEO. contains finds the text anywhere, also inside a word, and is slower.
company_nameNoCompany names. A comma means any of them. Prefer company_domain when you know the website.
exclude_cityNoCities to leave out. A comma means any of them.
has_linkedinNotrue keeps only people with a profile link.
revenue_bandNoYearly company revenue in US dollars, as bands. Pick one or more.
technologiesNoTechnologies the company uses, such as Shopify, HubSpot or AWS. A comma means any of them.
country_matchNoWhose place a country means. person (the default) counts people by where they are based and leaves out people whose own place is not known. person_or_company also counts them by their company's country.
employees_maxNoLargest number of employees, such as 500.
employees_minNoSmallest number of employees, such as 50. A company counts when its size range overlaps yours.
exclude_stateNoStates or provinces to leave out. A comma means any of them.
exclude_titleNoJob titles to leave out, matched the same way as title. A comma means any of them.
keyword_scopeNoWhere keywords look. company (the default) looks only at what the company does: its name, tags, industry and description, so a search for MSP finds people at managed service providers. Use people only when the user wants people who have a skill themselves, such as people who know Python or Salesforce admins at any company; it looks only at the person's own skills and profile. any looks at both, plus job titles. Without a value, company is used.
radius_targetNoWhose location counts. any (the default) is where the person is based, or where their company is when their own place is not known. person is only where the person is based, company only where their company is based.
verified_onlyNoDeprecated. It has no effect on the search and will be removed. Leave it out.
company_domainNoCompany website domains, such as stripe.com. A comma means any of them.
employee_rangeNoNumber of employees at the company: size bands (pick one or more), or one text value with a range like "1-500".
include_phonesNotrue also looks up phone numbers, at the phone price in the description. Off by default.
industry_matchNoHow industries match. any (the default) finds the industry anywhere in what the company is tagged with. primary only counts the company's main industry, so Software and Internet leaves out a retailer or a bank that also carries a software tag.
company_countryNoCountries or regions where the company has its head office, with the same names as country. Use it with country to get people in a country at companies based there. For people it works together with a list of company websites (company_domain) for now.
exclude_countryNoCountries or regions to leave out, matched the same way as country. A comma means any of them.
company_categoryNoWhat kind of company sells, used with sells_to. One of software, payments, pos_payments, business_fintech, accounting_software, payroll_hr_software, formation, association, marketplace or investors.
exclude_industryNoIndustries to leave out, matched the same way as industry. A comma means any of them.
exclude_keywordsNoWords to leave out, matched the same way as keywords. A comma means any of them.
exclude_seniorityNoSeniority levels to leave out. Pick one or more.
exclude_assistantsNoOn by default. A job title search leaves out assistant titles such as assistant to, executive assistant or personal assistant. Set it to false to keep them. The answer lists what it left out under applied_defaults, and a saved list keeps the setting.
business_email_onlyNoOnly people whose email is at their company's own domain. Off unless you set it, so private addresses are left out only on request. When it is on, the answer says so under applied_filters.
exclude_departmentsNoDepartments to leave out. Pick one or more.
exclude_title_matchNoHow the titles to leave out must match, with the same choices. When it is not set, the title choice is used.
exclude_company_domainNoCompany website domains to leave out. A comma means any of them.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description goes well beyond the annotations by disclosing the pricing model (1 credit per newly unlocked email, already-unlocked people are free), the phone surcharge (10 credits each, nothing if none found), that only working emails are shown and charged, and the existence of a daily safety cap. These are exactly the side effects an agent must know before a destructive/credit-spending call. The only minor gap is that it doesn't quantify the daily cap or describe the return shape, though an output schema exists.

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?

Front-loads purpose, then routing, then cost, in a sensible order, and nearly every sentence carries an actionable fact. It loses a point for redundancy ('Ask the user before you spend credits' appears twice in slightly different forms) and for the trailing docs link that adds little.

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

Completeness5/5

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

For a 52-parameter, credit-spending, open-world tool this covers everything an agent needs: what it returns, what it costs, which people are free, the phone surcharge, the safety limit, the filter lineage, and an instruction to relay the answer's summary to the user. The return format itself is delegated to the existing output schema, so nothing important is missing.

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?

Schema description coverage is 100%, so every one of the 52 parameters is already documented. The description adds only a little: that filters are identical to argorant_count_people, and the cost consequence of include_phones. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

States a specific verb and resource plus the exact payload ('full contact details (name, job, company, work email and profile link)'), and immediately distinguishes the scope as 'a small group of people who match a search'. That scope difference is what separates it from argorant_create_export and argorant_enrich, which are named.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('the few people the user wants now, after they approved the cost') and when-not ('for a file of many people use argorant_create_export, and for one known person use argorant_enrich or argorant_find_email'). It even points to argorant_count_people as the filter reference, so the agent knows how to construct the query.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.