Skip to main content
Glama

list_members

Lists members of a Google Chat space or direct message to identify participants, verify access, or prepare targeted messages.

Instructions

List members of a space or DM.

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": {
      "space_id": "<space_id>"
    },
    "name": "list_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
is_dmNo
space_idYes
page_sizeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.2/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden; it discloses scope (space vs DM) but not pagination behavior, result ordering, permission requirements, or whether DM member lists are restricted. Since an output schema is present, return-shape disclosure is not required, which keeps this from dropping further.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of waste, but at seven words it is under-specified rather than tight. Brevity here costs the reader the parameter and pagination context they need.

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

Completeness2/5

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

For a three-parameter tool with zero schema description coverage and no annotations, the definition omits too much: the role of is_dm, how page_size drives paging, and any access prerequisites. The existing output schema covers return values, but the input-side gaps remain substantial.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, so the description must compensate and does not. It never explains space_id (the only required param), the is_dm boolean, or the page_size default of 50—an agent cannot tell from the text whether is_dm must agree with the space_id or whether pagination must be driven manually.

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?

The description gives a clear verb plus resource ("List members") and narrows scope to "a space or DM," which distinguishes it from siblings like list_spaces and list_sections that enumerate other resources. It falls short of a 5 because it never contrasts itself with a similar roster-listing alternative or states that space_id identifies the container.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer it should call this when it needs the roster of a known space or DM. There is no explicit when-to-use versus when-not, no mention of required access or membership visibility, and no guidance on choosing between this and search_messages or get_user_status for people lookups.

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