Skip to main content
Glama

search_people

Read-onlyIdempotent

Search people by free text — names, companies, titles, skills, past roles, bios, and your own notes and tags all match. Known GitHub identities include github_login and github_url; github_user_id is a stable account ID, not a handle. Terms are OR-matched and ranked by how many match (more terms broadens, not narrows). To narrow: put AND between terms to require all (e.g. 'health AND medtech'), or prefix a term with + to require just it (e.g. '+rust berlin'). For roles/functions (founder, engineer, investor, …) use the role filter instead of free text — it catches title variants ('Founding Partner') that keywords miss, and free text also matches bios, past roles, and notes. To count people of a type, use structured filters and read total from the response — a free-text total counts keyword matches, not people of that type. scope:'own' (default) / scope:'public' (beyond your network + warm-intro paths) / scope:'team' (your pooled team network). Optional company, location, skills, tags, sources, and date filters apply in scope:'own' and scope:'team' (q is optional there — omit it to browse). A structured-filter zero = thin data, not absence — fall back to free text. Misspelled names/companies fall back to fuzzy matching (fuzzy: true = closest matches — confirm before trusting); in scope:'own', concept queries with zero literal hits then fall back to embedding similarity (semantic: true = related people, not literal matches). Free-text responses also return strong_total (rows matching ALL terms — the honest count) and per-row matched_on (which fields matched). In scope:'public', role/location/company/skills are applied to the global hits (filtered: true); filters that cannot apply there are listed in unsupported_filters.

Input Schema

NameRequiredDescriptionDefault
qNoFree-text query. Each term is matched (substring, accent-insensitive) against name, headline, current company, location, skills, GitHub repo languages/topics, bio, every linked account's names/usernames/headlines/bios and past roles (company + title). Your own people also match your recorded interactions, memories, notes and tags; a teammate's people (scope:'team') match only their public profile text, never the teammate's private history, notes or tags. Name hits rank highest; bio, past-role, note and tag hits rank lowest. Terms are OR-matched; operators narrow: uppercase AND between terms requires all of them; a +term prefix requires just that term (e.g. '+health medtech'). Optional in scope:'own'/'team' (omit to browse with filters). In scope:'public', operators only affect the your-network half of results; global hits are matched by semantic similarity.
roleNoFilter by function (matched against the headline and, in your own network, past titles): engineer, designer, product, gtm, founder, recruiter, investor, other. `gtm` covers sales/growth/marketing/partnerships/biz-dev; `other` is the catch-all for customer success, operations, legal, academia, etc. Matches any of the listed roles. Seniority (CEO, CTO, VP, etc.) is not a function — pass it in `q` instead.
tagsNoRequire all of these tags you've applied.
limitNoPage size (own/team: default 25, max 200; public: default 40, max 50).
scopeNo'own' (default) — your network only. 'public' — global match + warm-intro paths to people you don't know yet. 'team' — your POOLED TEAM network (people known by ANY teammate), with the same filters and exact `total` as 'own' (no cap; page with offset/limit). Each team hit carries `team_members` (who on the team knows them, their consent-gated strength and teams), `team_ids`, and `primary_team_id` — pass that as get_person's team_id.
staleNoOnly people you've never interacted with, or not in 90+ days.
offsetNoPagination offset.
recentNoOnly people you've interacted with in the last 14 days.
skillsNoRequire all of these skills.
companyNoFilter by company — substring match on current OR former employers (each hit's `company_match` says which). In scope:'public' only the current company is checked.
sourcesNoRestrict to people who came from any of these sources.
team_idNoFor scope:'team' — the team_id of one team to search (from account_status.teams). Omit it to search every team you're in (a person several teams share is one hit, with all their `team_ids`). A team you don't belong to is rejected.
locationNoFilter by location (substring match; common aliases such as NYC/New York, SF/Bay Area, Lisbon/Lisboa expand).
added_afterNoOnly people added to your network ON/AFTER this date (ISO, e.g. 2026-06-01). For "who did I add this week / since X?". Adding ≠ interacting — for interaction recency use recent/stale.
added_beforeNoOnly people added STRICTLY BEFORE this date (ISO).
last_interaction_afterNoOnly people whose last recorded touchpoint was ON/AFTER this date (ISO, e.g. 2026-06-22 or 2026-06-22T00:00:00Z). Use for 'who did I interact with on/since <date>' or 'everyone with a touchpoint this week'. People with no interaction are excluded. Combine with last_interaction_before for a date range.
last_interaction_beforeNoOnly people whose last recorded touchpoint was STRICTLY BEFORE this date (ISO, exclusive upper bound). People with no interaction are excluded. Combine with last_interaction_after for a date range.

Output Schema

NameRequiredDescriptionDefault
okYesWhether noticed completed the operation.
dataNoThe operation result when ok is true.
errorNoA human-readable error when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / team_id / description
      Previous value: -"For scope:'team' — the team_id of the team to search (from account_status.teams). Optional when you're in exactly one team; required to pick when you're in more than one. A team you don't belong to is rejected."New value: +"For scope:'team' — the team_id of one team to search (from account_status.teams). Omit it to search every team you're in (a person several teams share is one hit, with all their `team_ids`). A team you don't belong to is rejected."
  2. Changed6 schema fields changed
    • changedInput schema / properties / company / description
      Previous value: -"Filter by company (matches current + former employers)."New value: +"Filter by company — substring match on current OR former employers (each hit's `company_match` says which). In scope:'public' only the current company is checked."
    • changedInput schema / properties / limit / description
      Previous value: -"Page size (default 25, max 200 for own / 50 for public)."New value: +"Page size (own/team: default 25, max 200; public: default 40, max 50)."
    • changedInput schema / properties / location / description
      Previous value: -"Filter by location (substring match)."New value: +"Filter by location (substring match; common aliases such as NYC/New York, SF/Bay Area, Lisbon/Lisboa expand)."
    • changedInput schema / properties / q / description
      Previous value: -"Free-text query — matched OR-style against name, headline, company, location, skills, languages, topics, bio and linked-profile text (your own people also on your notes, tags and history; teammates' people never on theirs). The same matching applies to scope:'own' and scope:'team'. Operators narrow: uppercase AND between terms requires all of them; a +term prefix requires just that term (e.g. '+health medtech'). In scope:'public', operators only affect the your-network half of results; global hits are matched by semantic similarity."New value: +"Free-text query. Each term is matched (substring, accent-insensitive) against name, headline, current company, location, skills, GitHub repo languages/topics, bio, every linked account's names/usernames/headlines/bios and past roles (company + title). Your own people also match your recorded interactions, memories, notes and tags; a teammate's people (scope:'team') match only their public profile text, never the teammate's private history, notes or tags. Name hits rank highest; bio, past-role, note and tag hits rank lowest. Terms are OR-matched; operators narrow: uppercase AND between terms requires all of them; a +term prefix requires just that term (e.g. '+health medtech'). Optional in scope:'own'/'team' (omit to browse with filters). In scope:'public', operators only affect the your-network half of results; global hits are matched by semantic similarity."
    • changedInput schema / properties / role / description
      Previous value: -"Filter by function (matched against headline): engineer, designer, product, gtm, founder, recruiter, investor, other. `gtm` covers sales/growth/marketing/partnerships/biz-dev; `other` is the catch-all for customer success, operations, legal, academia, etc. Matches any of the listed roles. Seniority (CEO, CTO, VP, etc.) is not a function — pass it in `q` instead."New value: +"Filter by function (matched against the headline and, in your own network, past titles): engineer, designer, product, gtm, founder, recruiter, investor, other. `gtm` covers sales/growth/marketing/partnerships/biz-dev; `other` is the catch-all for customer success, operations, legal, academia, etc. Matches any of the listed roles. Seniority (CEO, CTO, VP, etc.) is not a function — pass it in `q` instead."
    • changedInput schema / properties / team_id / description
      Previous value: -"For scope:'team' — the organizationId of the team to search (from account_status.teams). Optional when you're in exactly one team; required to pick when you're in more than one. A team you don't belong to is rejected."New value: +"For scope:'team' — the team_id of the team to search (from account_status.teams). Optional when you're in exactly one team; required to pick when you're in more than one. A team you don't belong to is rejected."
  3. Changed3 schema fields changed
    • changedInput schema / properties / q / description
      Previous value: -"Free-text query — matched OR-style against name, headline, company, location, skills. Operators narrow your own network: uppercase AND between terms requires all of them; a +term prefix requires just that term (e.g. '+health medtech'). In scope:'public', operators only affect the your-network half of results; global hits are matched by semantic similarity."New value: +"Free-text query — matched OR-style against name, headline, company, location, skills, languages, topics, bio and linked-profile text (your own people also on your notes, tags and history; teammates' people never on theirs). The same matching applies to scope:'own' and scope:'team'. Operators narrow: uppercase AND between terms requires all of them; a +term prefix requires just that term (e.g. '+health medtech'). In scope:'public', operators only affect the your-network half of results; global hits are matched by semantic similarity."
    • changedInput schema / properties / scope / description
      Previous value: -"'own' (default) — your network only. 'public' — global match + warm-intro paths to people you don't know yet. 'team' — your POOLED TEAM network (people known by ANY teammate); each hit carries `team_members` (who on the team knows them + their consent-gated strength)."New value: +"'own' (default) — your network only. 'public' — global match + warm-intro paths to people you don't know yet. 'team' — your POOLED TEAM network (people known by ANY teammate), with the same filters and exact `total` as 'own' (no cap; page with offset/limit). Each team hit carries `team_members` (who on the team knows them, their consent-gated strength and teams), `team_ids`, and `primary_team_id` — pass that as get_person's team_id."
    • addedOutput schema / properties / data / properties / teams
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "id": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "name"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": true,
      +  "properties": {
      +    "data": {
      +      "additionalProperties": true,
      +      "description": "The operation result when ok is true.",
      +      "properties": {
      +        "hasMore": {
      +          "type": "boolean"
      +        },
      +        "hits": {
      +          "items": {
      +            "$ref": "#/properties/data/properties/people/items"
      +          },
      +          "type": "array"
      +        },
      +        "limit": {
      +          "type": "number"
      +        },
      +        "offset": {
      +          "type": "number"
      +        },
      +        "people": {
      +          "items": {
      +            "additionalProperties": true,
      +            "properties": {
      +              "company": {
      +                "$ref": "#/properties/data/properties/people/items/properties/person_id"
      +              },
      +              "display_name": {
      +                "type": "string"
      +              },
      +              "headline": {
      +                "$ref": "#/properties/data/properties/people/items/properties/person_id"
      +              },
      +              "id": {
      +                "type": "string"
      +              },
      +              "name": {
      +                "type": "string"
      +              },
      +              "person_id": {
      +                "type": [
      +                  "string",
      +                  "null"
      +                ]
      +              }
      +            },
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "scope": {
      +          "enum": [
      +            "own",
      +            "team",
      +            "public"
      +          ],
      +          "type": "string"
      +        },
      +        "strong_total": {
      +          "type": "number"
      +        },
      +        "total": {
      +          "type": "number"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "error": {
      +      "description": "A human-readable error when ok is false.",
      +      "type": "string"
      +    },
      +    "ok": {
      +      "description": "Whether noticed completed the operation.",
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "ok"
      +  ],
      +  "type": "object"
      +}
  5. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description still discloses OR-matching and ranking order, AND/+ narrowing operators, fuzzy fallback on misspellings, embedding fallback for concept queries in scope:'own', and how scope:'public' applies filters with `filtered`/`unsupported_filters` reporting. These are behaviors an agent could not infer from annotations alone.

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

Conciseness3/5

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

All content is substantive, but it is delivered as one long unbroken paragraph mixing matching semantics, filtering advice, scope behavior, and fallback rules — much of which duplicates the very detailed schema descriptions. Front-loading the matching model is good; the density makes it harder to scan than it needs to be.

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 17-parameter tool with zero required params, an output schema, and full annotation coverage, the description covers the behaviors that matter: matching model, scope semantics, fallback paths, and how to read `total`/`strong_total`/`matched_on`. Nothing an agent needs to call it correctly is missing.

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% and the schema descriptions are already detailed, so baseline is 3; the description still adds decision-relevant meaning — the distinction between free-text `total` (keyword matches) and people of a type, and why `role` beats keywords for functions. It stops short of restating per-parameter syntax, which is correct given the schema.

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?

Opens with a specific verb and resource ('Search people by free text') and immediately enumerates the matched fields — names, companies, titles, skills, past roles, bios, notes, tags. It is clearly differentiable from siblings such as get_person (single fetch), network_summary (aggregates) and resolve_person (identity work).

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?

Explicit routing guidance: use the `role` filter instead of free text for functions because keywords miss title variants; use structured filters plus `total` to count people of a type; use recent/stale for interaction recency, added_after for network-adding; and fall back to free text when a structured filter returns zero. Names the alternatives and the conditions that select them.

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