Skip to main content
Glama

Particle Company List People

particle_company_list_people
Read-only

List the people at one company, leadership first, a page at a time: the chief executive, then founders, chairs and presidents, the rest of the C-suite, board members, EVPs, SVPs, VPs, directors, managers, and everyone else, the longest-serving first within a level. Each entry gives the person slug and their title at this company, with the total across all pages.

Use it to go past the 25-person preview particle_company_get include=people returns, or to narrow a large company with role (e.g. executive), title (e.g. 'chief', 'investor relations') or name (e.g. 'huang'). For one company's profile and its leadership at a glance, call particle_company_get instead. To find a person by name, use particle_person_resolve.

Person slugs feed particle_person_get, particle_person_get_statement_characteristics, and the person_slug filter of particle_podcast_find_mentions, particle_podcast_search_transcripts and particle_podcast_list_episodes. For how the company's people speak on podcasts together, use particle_company_get_statement_characteristics.

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": {
      "company_slug": "<company_slug>"
    },
    "name": "particle_company_list_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoCase-insensitive substring of the person's name (e.g. 'huang'), to find someone at a large company. To find a person by name across every company, use particle_person_resolve.
roleNoOnly people whose title falls in this role class. executive is the leadership class: founders, chairs, presidents, VPs, directors and heads whose title names none of the other classes' functions, plus every officer (any Chief ... Officer or President) whatever function the title names. So a Chief Marketing Officer is kept but a VP of Marketing is marketing. marketing, brand, partnerships, media_advertising, communications and growth are the functions a sponsorship pitch would reach; other is a title matching none.
sortNoseniority (default): leadership first, the longest-serving first within a level. recent: the most recently started first.
limitNoPeople per page (1-100, default 25).
titleNoCase-insensitive substring of the title at this company (e.g. 'chief', 'founder', 'investor relations').
cursorNoOpaque pagination cursor from a previous response's cursor field. Pass the same filters and sort with it.
company_slugYesCompany identifier — slug (e.g. 'nvidia'), domain (e.g. 'nvidia.com'), or canonical ID, as particle_company_get takes.
include_pastNoAlso list people who held a role here and no longer do, marked (former), after everyone current. Default false.
output_formatNoOutput serialization. 'markdown' (default) returns the LLM-facing rendering. 'json' returns the structured payload as JSON text — use only for programmatic chaining where exact field extraction matters; the JSON shape is larger and noisier for an LLM to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint=false, so the safety profile is covered; the description adds genuine beyond-schema behavior: results come paged with a total across all pages, past holders are appended and marked '(former)', and ordering is tie-broken by tenure. It stops short of disclosing data-freshness or coverage limits for a company's roster, which is the remaining behavioral unknown.

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?

It is front-loaded with purpose and ordering, then usage, then pagination filters, then downstream chaining — a sensible progression. It runs four paragraphs and the long seniority enumeration plus repeated tool references cost some length, but almost every sentence carries routing or behavioral 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?

With no output schema, the description carries the return-value burden and does it: it names the fields per entry (slug, title), the total count, the '(former)' marker, and the markdown-vs-json tradeoff. For a 9-parameter, paginated, filterable list tool this is sufficient for correct invocation.

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

Parameters3/5

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

Schema description coverage is 100% and the description's parameter examples ('huang', 'chief', 'investor relations', 'executive') largely restate what the schema already documents, so added semantic value is marginal. The one genuinely additive note is the filter-narrowing strategy for large companies, but the per-parameter meaning stays with the schema; baseline 3 applies.

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 first clause gives a specific verb and resource ('List the people at one company') plus the ordering contract (leadership first, a page at a time) and the per-entry payload (person slug, title, total count). It explicitly separates itself from `particle_company_get` and `particle_person_resolve`, so an agent can pick it without opening the 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?

It states the trigger condition ('go past the 25-person preview `particle_company_get` include=people returns'), names alternatives with their selecting conditions (`particle_company_get` for a profile at a glance, `particle_person_resolve` for cross-company name lookup), and lists the downstream tools consuming the returned slugs. Both when-to-use and when-not-to-use are covered.

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