Skip to main content
Glama

Get account map people

get_account_map_people
Read-only

List people at one account with their influence roles, seniority, department and up to 3 best warm paths each (teammate, strength, one-line summary). Defaults to the buying committee, sorted reachable first then by seniority; set the COMMITTEE_ONLY filter to "false" to search the whole directory of current employees. Supports name/title text search, filters and paging. Each person carries a person_key; pass it to get_account_map_person for every path and likely managers.

Use when: Use to name the people on a buying committee, find who holds a given influence role (INFLUENCE_ROLE filter), or find the warmest way in (REACHABLE_ONLY filter or sort STRENGTH). Use get_account_map_summary first for the role-level coverage picture. Needs the internal account UUID: resolve the account first with search_accounts_with_filters. To find people at a company that has no account record use search_people_in_companies.

Behavior: read_only

workspace_id / user_id are injected from request headers.

Returns people[] with fields:

person_key full_name title linkedin_url seniority influence_roles department contact_id influence_roles_source path_count kept_path_count paths avatar_url Also returns pagination info (current_page_number, page_size, total_pages, total_elements).

IMPORTANT: If the response contains more than one record, always present the options to the user and ask them to choose before taking any follow-up action. Do not act on all results automatically.

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

Input Schema

NameRequiredDescriptionDefault
sortNo
filtersNoOptional filters; values within one filter are OR-combined, different fields are AND-combined. Fields: INFLUENCE_ROLE (role keys such as economic_buyer, champion), SENIORITY (IC, MANAGER, DIRECTOR, VP, CXO), DEPARTMENT (title-derived department key), WARMTH (CONFIRMED, STRONG, LESS_LIKELY), COMMITTEE_ONLY ("true" default, "false" = whole directory), REACHABLE_ONLY ("true" = only people with a kept path), COLUMN (board column key, e.g. REVENUE, FINANCE), EXCLUDE_KEYS (person_keys to omit).
page_sizeNo
path_ruleNo
account_idNo
page_numberNo
search_textNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, non-open-world profile, so the description earns credit for what it adds: default committee-only scoping, default sort order (reachable first, then seniority), workspace_id/user_id injection from request headers, and the multi-result handling rule. It stops short of stating rate limits or whether nested path data is truncated beyond the 'up to 3' cap, but the mutation/safety profile is fully consistent with the annotations.

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, then partitioned into 'Use when', 'Behavior', 'Returns' and 'IMPORTANT' sections that are easy to scan. Some content is redundant — 'Behavior: read_only' repeats the annotations and the field list restates the output schema — but the remaining sentences carry real routing and default information.

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 7-parameter, header-injected query tool, the definition supplies the prerequisite (resolve the account UUID first), the default scoping and ordering, the downstream handoff (pass person_key to get_account_map_person), pagination existence, and the multi-result interaction rule. With an output schema present, the inline field list is superfluous but nothing an agent needs in order 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 description coverage is low (14%), so the description must compensate, and it largely does: it explains account_id must be the internal account UUID obtained via search_accounts_with_filters, the COMMITTEE_ONLY 'false' escape hatch to the whole directory, INFLUENCE_ROLE and REACHABLE_ONLY filters, sort=STRENGTH, name/title text search, and paging. Only path_rule and the exact sort enum vocabulary go unaddressed, leaving a small gap.

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?

The opening sentence names a specific verb and resource ('List people at one account') plus exactly what each record contains: influence roles, seniority, department and up to 3 warm paths. It is clearly distinguishable from get_account_map_person (single person), get_account_map_summary (role-level picture) and search_people_in_companies (companies without an account record).

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?

An explicit 'Use when:' block gives three concrete scenarios (naming committee members, finding an influence role, finding the warmest path) and names the alternatives with the condition that selects them: get_account_map_summary 'first' for coverage, search_accounts_with_filters to resolve the UUID, search_people_in_companies for companies lacking an account. The IMPORTANT block also tells the agent not to act on multiple results without user choice.

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