Skip to main content
Glama

List people

list_people
Read-onlyIdempotent

Lists the authors of mentions of your keywords. Each has name, profile, platform, how many posts matched and how many scored relevant, sentiment split, first and last seen, and outreach status (owner, stage, last contacted). You can filter by platform or name, find one person by handle or profile link (handle), and filter by outreach stage (stages), owner (ownerIds, or "none" for no owner) or automated (bots whose posts are mostly machine-made). Sort by mentions or by recency. To read what one person said, use search_mentions with personId.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearches the display name, handle and profile link
tagNoKeeps people with this tag
sortNo"mentions" puts the most matches first, "recent" the most recently seen, "reach" the most followers, and "new" people seen for the first time most recentlymentions
tagsNoKeeps people with one of these tags
limitNo
mutedNotrue keeps muted people and false people who are not muted. Leave it out for everyone
sinceNoKeeps people whose first matched mention is at this time or later, as ISO 8601 or epoch ms. Use it to find new voices
handleNoLooks up one person by an account, given as a handle (@sam, u/sam) or a profile or post link (https://x.com/sam). The match is exact but ignores case. Add platform to pick one platform
offsetNoHow many people to skip, for paging
stagesNoOnly people in one of these outreach stages
intentsNoHas a mention tagged with one of these intents
ownerIdsNoKeeps people owned by one of these members, by user id. Use "none" for people without an owner
platformNoOnly people with a profile on this platform
automatedNotrue keeps people whose matched posts are mostly machine-made, such as bots. false keeps the others
linkHostsNoKeeps people with a mention that links to one of these hosts or its subdomains, so slack.com also matches api.slack.com
platformsNoKeeps people with an account on one of these platforms
segmentIdNoAdds a saved segment's filter (from list_segments) to the other filters
minMentionsNoMinimum number of matched mentions
minNegativeNoMinimum number of negative mentions
keywordKindsNoKeeps people who mentioned a keyword of one of these kinds (brand, competitor, topic)
maxFollowersNo
minFollowersNoKeeps people with this many followers or more. Unknown counts are left out
newSinceDaysNoKeeps people first seen in the past this many days
neverKeywordKindsNoExcludes people who mentioned these keyword kinds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "bluesky",
      -  "hackernews",
      -  "github",
      -  "stackoverflow",
      -  "devto",
      -  "reddit",
      -  "x",
      -  "youtube",
      -  "news",
      -  "linkedin",
      -  "tiktok",
      -  "instagram",
      -  "appstore",
      -  "googleplay",
      -  "trustpilot",
      -  "googlemaps"
      -]New value: +[
      +  "bluesky",
      +  "hackernews",
      +  "github",
      +  "stackoverflow",
      +  "devto",
      +  "reddit",
      +  "x",
      +  "youtube",
      +  "news",
      +  "linkedin",
      +  "tiktok",
      +  "instagram",
      +  "appstore",
      +  "googleplay",
      +  "trustpilot",
      +  "googlemaps",
      +  "rss"
      +]
    • changedInput schema / properties / platforms / items / enum
      Previous value: -[
      -  "bluesky",
      -  "hackernews",
      -  "github",
      -  "stackoverflow",
      -  "devto",
      -  "reddit",
      -  "x",
      -  "youtube",
      -  "news",
      -  "linkedin",
      -  "tiktok",
      -  "instagram",
      -  "appstore",
      -  "googleplay",
      -  "trustpilot",
      -  "googlemaps"
      -]New value: +[
      +  "bluesky",
      +  "hackernews",
      +  "github",
      +  "stackoverflow",
      +  "devto",
      +  "reddit",
      +  "x",
      +  "youtube",
      +  "news",
      +  "linkedin",
      +  "tiktok",
      +  "instagram",
      +  "appstore",
      +  "googleplay",
      +  "trustpilot",
      +  "googlemaps",
      +  "rss"
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by enumerating the fields returned per person (mentions, relevance, sentiment split, outreach status), which partially compensates for the absent output schema, but says nothing about pagination, rate limits, or result ordering behavior beyond sort options.

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?

Four front-loaded sentences: purpose and return shape first, then filtering, then sorting, then the alternative tool. Dense but every sentence carries a distinct idea, though the filter recap partially overlaps the schema.

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 a 24-parameter list tool with no output schema, the description supplies the returned field list and a routing hint, which is enough for correct invocation. Minor gaps remain around paging behavior and total-count semantics, but the structured schema covers the filter surface well.

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 92%, so the schema already documents nearly every parameter. The description restates platform/name/handle/stages/ownerIds/automated and the 'none' owner sentinel, which duplicates rather than extends the schema; baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Lists the authors of mentions of your keywords') and immediately names the returned entity's shape. An agent can distinguish this from get_person (single person) and search_mentions (posts, not people) without opening a schema.

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

Usage Guidelines4/5

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

Explicitly routes the agent to search_mentions with personId to read what one person said, and notes the handle lookup for a single person. It gives clear context but does not contrast against get_person, which is the closest sibling and an obvious alternative.

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.