Skip to main content
Glama

graph_list_chat_members

Retrieves members of a chat, with optional pagination via next_link, to identify participants and continue through large member lists.

Instructions

List members of a chat.

Args: chat_id: The chat ID. 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": {
      "chat_id": "<chat_id>"
    },
    "name": "graph_list_chat_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idYes
next_linkNo
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations present, the description carries the full disclosure burden. It does useful work by stating the return shape (bare list by default, or {items, next_link} when include_next_link is true) and the paging override rule, which goes beyond the schema. It omits permission requirements, whether results are complete or a page subset, and typical error conditions for a non-member chat ID.

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?

The purpose leads in a single short sentence, followed by a compact Args block with no redundant prose. It is appropriately sized for a three-parameter read tool; only minor verbosity in the wrapped next_link explanation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read operation the definition covers parameters and return shape adequately, which is most of what an agent needs. It lacks any statement of auth/permission requirements and no output schema exists to cover return semantics, leaving a moderate gap for a tool with zero annotations.

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 0%, so the description must supply all parameter meaning, and it does for all three: chat_id, next_link as an opaque URL from a prior call that overrides other paging arguments, and include_next_link with its default and effect. The one gap is that chat_id's expected format (Graph object ID vs email/UPN) is never stated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List members of a chat" gives a specific verb and resource, and the phrase "of a chat" implicitly distinguishes it from the sibling listers for channel and team members. It stops short of naming those alternatives explicitly, so the differentiation rests on the reader inferring it from the resource word.

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

Usage Guidelines2/5

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

There is no statement of when to prefer this tool over graph_list_channel_members or graph_list_team_members, and no preconditions such as required permissions or the fact that the caller must already know the chat ID. The only usage-adjacent content is paging mechanics (next_link overrides other paging args), which is operational rather than selection guidance.

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