Skip to main content
Glama

SourceGeek

Search employees

employee_search_people
Read-only

Search employee data by keywords, title keyword, first/last name, current company, school and geo id. Returns fullName, headline, location, username and profile URL per hit plus the total; pages of 10 via start (0, 10, 20…). Non-public profiles are filtered out, so pages can be short.

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

Input Schema

NameRequiredDescriptionDefault
geoIdNoGeo id (numeric part, e.g. '102011674').
limitNoMaximum items to return (1-100, default 10). Results beyond the provider's page are not fetched.
startNoProvider offset for the next page (echoed back as nextStart by the previous call). Omit for the first page.
companyNoCurrent company name keyword.
keywordsNoFree-text keywords (e.g. 'recruiter fintech').
lastNameNo
schoolIdNoNumeric school id.
firstNameNo
keywordTitleNoKeyword that must appear in the current title.
keywordSchoolNo
currentCompanyIdsNoNumeric company ids to restrict current employer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds genuinely new behavior: the per-hit return fields (fullName, headline, location, username, profile URL), a total count, and — most usefully — that non-public profiles are filtered out so pages can come back short. The pagination story is muddled though: it says "pages of 10 via start (0, 10, 20…)" while the schema exposes a limit up to 100, so the agent cannot tell which controls page size.

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?

Two tight sentences, front-loaded with the resource and filters, then the return shape, then a non-obvious caveat about filtered profiles. Nothing is padding. Minor deduction only because the pagination clause is both terse and inaccurate relative to the limit parameter.

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 an 11-parameter, zero-required search tool with no output schema, this covers a lot: filter vocabulary, response fields, total count, and a short-page caveat. The gaps are the interaction between filters and the page-size contradiction; an agent still has to guess whether calling with no filters is valid or expensive.

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 73%, so the schema carries most parameter documentation. The description adds real value on pagination semantics (start is a provider offset, first page at 0, echoed next-page cursor) and on the filtering model, but it does not clarify how the many optional filters combine, nor does it explain whether keywords and keywordTitle/keywordSchool are ANDed — and the "pages of 10" claim conflicts with the schema's limit 1-100.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Search employee data") and enumerates the filter dimensions the tool keys on (keywords, title keyword, first/last name, current company, school, geo id). It is unambiguous against siblings like employee_search_companies or employee_search_jobs because the resource is named explicitly, though it never calls out the distinction itself.

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

Usage Guidelines3/5

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

Usage is implied by the enumerated filter vocabulary — an agent can infer this is the people-lookup tool when it has name/company/school signals. However, there is no explicit when-to-use versus the many sibling search tools, no statement that all parameters are optional or that at least one filter should be supplied, and no guidance on preferring employee_search_* variants over fast_search_* / precision_search_* routes.

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