Skip to main content
Glama

Search people

search_people
Destructive

Use this when the user wants to find people: by a plain-language description (such as "operations directors at logistics companies in Portugal"), by filters, by a saved search, or one person by LinkedIn URL. Send exactly one of query, filters, savedSearchId or savedSearchName. Returns one page of people with their job, company and location, and the filters the search ran with; for the next page, send those filters with the page's next cursor. People never carry an email address or a phone number: finding those is a separate, paid enrichment. Costs $0.001 per person returned, charged to the organization's balance; a page with nobody on it is free. Calling again with the same arguments charges again.

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": "search_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPeople per page. The page's most possible cost, `limit` times $0.001, is held from your balance first.
queryNoWho to find, in plain language. It is turned into filters, which the page answers with as `filters`.
cursorNoThe `pagination.nextCursor` of the page before. Send it with the same search, as the `filters` the first page answered with.
detailNoHow much of each row to return. `short` (the default) leaves out the long fields; `full` returns every field, so ask for few rows with it.short
filtersNoFilters by name. Each filter's allowed values are listed with the people filters; free-text filters (job titles, companies, websites, locations, regions, schools, skills) take a suggested value.
linkedinUrlNoLook up one person by a LinkedIn profile URL, `in/<slug>` or the bare slug. It counts as a search on its own, or narrows one.
savedSearchIdNoRun a saved people search by its id.
savedSearchNameNoRun a saved people search by its title. A title several saved searches share answers 409 `saved_search_name_ambiguous`.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only mark it non-idempotent and destructive; the description supplies the substance behind that: $0.001 per person, charged to the org balance, re-running the same arguments charges again, and an empty page is free. It also declares a hard data boundary (no email or phone in results) and explains pagination via the page's nextCursor. This is materially more than the annotations convey and is consistent with destructiveHint=true (the call consumes balance).

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-loaded with the trigger and mode selection, then cost and pagination, with no filler sentences. It is dense and runs long across several clauses, but every sentence carries information an agent needs.

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 an 8-parameter, nested-object tool with no output schema, the description still covers what a page returns (job, company, location plus the resolved filters), how to page, and what is deliberately absent from results. Combined with the cost model, an agent has everything needed to call it correctly and to anticipate the charge.

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?

Schema coverage is 100%, so most parameter meaning is already structured, but the description adds the one-of constraint across query/filters/savedSearchId/savedSearchName that the schema does not encode, explains that linkedinUrl counts as a search on its own or narrows one, and describes the cursor handoff. This is real added value rather than restatement, though a few clauses mirror the schema text.

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 (find people) and enumerates the distinct search modes: plain-language query, filters, saved search by id or name, or a single LinkedIn URL. An agent can distinguish this from count_people, enrich_people or run_saved_search from the description alone.

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 an explicit trigger ("when the user wants to find people") plus an exclusivity rule for the four search entry points, and routes email/phone needs away to "a separate, paid enrichment" (i.e. enrich_people). Nothing is left to inference about when this is the right call.

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.

Resources