Skip to main content
Glama

graph_search_people

Search colleagues, saved contacts, and external people by name, email, or partial text to find someone the signed-in user works with, ranked by relevance.

Instructions

Search people the user works with, ranked by relevance.

Covers colleagues, saved contacts, and external people the user has mailed, so prefer this over graph_search_users when looking someone up by name. $search on /me/people only works for the signed-in user, and Graph does not support $skip alongside it, so page with next_link instead of an offset. Requires the People.Read permission.

Args: query: Name, email address, or partial text to look up. top: Maximum number of people to return (default 10, maximum 50). compact: Whether to return only the identifying fields instead of the full record (default false). Use it to page through large collections cheaply. next_link: Opaque nextLink URL from a previous call, used to fetch the next page. Overrides the other paging arguments when supplied. include_next_link: Whether to wrap the result as {items, next_link} so paging can continue (default false, which returns a bare list).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "graph_search_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
queryYes
compactNo
next_linkNo
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the required People.Read permission, a Graph API limitation on $search scoping, the absence of $skip paging, and the two possible return shapes (bare list vs {items, next_link}). It stops short of describing throttling, error behavior, or result ordering guarantees beyond "relevance".

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 purpose and the sibling comparison before the Args block, and each sentence carries information (paging caveat, permission, per-argument notes). Slightly verbose in the Args section where the parenthetical defaults restate what is already in the schema, but nothing is filler.

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 and no annotations, so the description must explain both behavior and the return contract; it does by defining include_next_link as wrapping results into {items, next_link}. Permission requirements, paging mechanics, and cost tradeoffs of compact mode are all covered, leaving nothing an agent needs in order to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate and does: all five parameters are documented with meaning, defaults, and interactions. It adds real constraint beyond the schema, notably that top defaults to 10 with a maximum of 50 (the schema itself allows an unbounded integer) and that next_link overrides the other paging arguments.

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 ("Search people the user works with, ranked by relevance") and defines scope as colleagues, saved contacts, and external correspondents. It explicitly names the sibling it is not (graph_search_users), so an agent can route between them without opening either 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?

Gives an explicit when-to-use rule: "prefer this over graph_search_users when looking someone up by name." It also states a hard constraint ($search only works for the signed-in user, no $skip) and tells the agent to page with next_link instead of an offset, which is operative guidance rather than background.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools