Skip to main content
Glama

Count people

count_people
Read-only

Use this when the user wants to know how many people match a search before paying to list them. Send exactly one of query, filters, savedSearchId or savedSearchName, as a people search takes them. A new count runs in the background: while the answer's status is pending, call again with the same arguments every few seconds until the status is ready and the total is there. A count can take up to a minute and a half. Free. It returns a number, never the people.

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

Input Schema

NameRequiredDescriptionDefault
queryNoWho to find, in plain language. It is turned into filters, which the page answers with as `filters`.
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.
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.9/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, openWorld, non-destructive). The description adds the context that actually matters here: the count runs asynchronously, must be re-polled with identical arguments until status is ready, can take up to 90 seconds, and is free.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the when-to-use, then the argument rule, then the polling contract, then cost and return type. Every sentence carries a distinct, actionable fact with no filler or restatement of the title.

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?

No output schema exists, so the description supplies the return contract (a number, not people) and the async status lifecycle. Combined with the full schema documentation and safety annotations, an agent has everything needed to call and poll this tool correctly.

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 field-level meaning and examples are already handled. The description still adds a cross-parameter rule the schema cannot express: exactly one selector must be supplied, treated like a people search.

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 (count people matching a search) and explicitly contrasts the return type with the alternative: 'It returns a number, never the people.' That singles it out from siblings like search_people without needing the other schema.

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?

Names the trigger condition ('when the user wants to know how many people match a search before paying to list them') and gives an explicit usage rule: send exactly one of query, filters, savedSearchId, savedSearchName. Nothing about when to invoke is left to inference.

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