Skip to content
Graviola

Find the right people

Search the intended audience without losing the requirements.

Define the audience

  • Role: the job or buying role you want.
  • Location: country, city or another supported geographic filter.
  • Requirements: experience, skills, education or company criteria.
  • Target: how many useful results you need.
  • Budget: the maximum searches, profiles and contact reveals to process.

Make the criteria executable

In a structured search, the query is a description. The filters perform the search. A query saying software engineer does not replace a title filter. Country and email filters alone can return unrelated people. Your assistant should translate the brief, not ask you to write API parameters.

IntentFilter or check
Software engineerstitle: ["software engineer", "engenheiro de software"]
United Statescountry: ["US"]
Brazilcountry: ["BR"]
An available emailhasEmail: true
A particular school or fieldeducation: ["school or field"], followed by profile review
10 years of experienceCheck dated career periods after loading the profile.

Start with contactable profiles

The initial MCP search selects people with available email and a LinkedIn profile. Email verification is not required by this selection. Unknown availability, no email, and no LinkedIn are different conditions. A missing field must not be invented.

A profile without a LinkedIn link may still load by its stored person ID. It remains a discovery until the required evidence is available.

Review the best matches first

Interactive searches use relevance ranking. Stable ordering is for walking a large result set, not choosing the initial shortlist. Continue pagination with the original search criteria and ordering.

Reuse saved work

Open the saved search to review it again. In MCP, search_results reads existing results without another search or reveal. The assistant should use returned references instead of inventing profile or candidate IDs.

If an interrupted operation is retried, preserve the exact requestId and parameters. A genuinely different search needs a new requestId. Viewing incomplete saved profiles is different from paying for another search.

Hiring example

Find 3 senior software engineers in Brazil. Require Python and 10 years of dated professional experience. Start with one search and review at most 5 profiles. Load career and education, separate supported matches from missing evidence, and do not reveal contacts or send email yet.

Sales example

Find 5 founders of US software companies that sell developer tools. Require an available email, LinkedIn profile and evidence of their current role. Keep unsupported company criteria separate. Use one search and review at most 5 people. Do not send messages.
NextReview profiles correctly ↗