Skip to main content
Glama
loomiomcp
by soil-dev

list_memberships

Read-onlyIdempotent

List a group's members to resolve names to user_id and verify membership before managing members. Returns paginated users, memberships, and total; non-members get an empty list, not an error.

Instructions

A group's members: 1 call. Returns memberships[] (user_email only on rows Loomio grants an admin or inviter, never read-only), users[], total. Use it to resolve a name to a user_id and ALWAYS before manage_memberships with remove_absent. A non-member gets an EMPTY list, not 403: never report it as an empty group.

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": {
      "group_id": "<group_id>"
    },
    "name": "list_memberships"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, 1-200. Default 50.
offsetNoPage offset. Default 0.
group_idYesGroup id (a non-member gets an empty list, not 403).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.0.13
    • changedInput schema / properties / group_id / description
      Previous value: -"ID of the Loomio group whose memberships to list (required). The connector's bot user must be an admin (coordinator) of the group — Loomio only returns the member list, including email addresses, to group admins. For a non-admin bot this returns a clear 403 explaining the role requirement; names/usernames/ids (not emails) are still reachable via get_user_activity / list_events."New value: +"Group id (a non-member gets an empty list, not 403)."
    • changedInput schema / properties / limit / description
      Previous value: -"Page size. Loomio defaults to 50."New value: +"Page size, 1-200. Default 50."
    • changedInput schema / properties / offset / description
      Previous value: -"Page offset. Defaults to 0."New value: +"Page offset. Default 0."
  2. First observedv0.0.6

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior, but the description adds substantial beyond that: the return structure (memberships[], users[], total), the permission-based limitation on user_email visibility, and the critical edge case that non-members receive an empty list rather than a 403. This is excellent behavioral disclosure.

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 description is dense and front-loaded, packing return shape, usage guidance, and edge case into a few sentences with zero waste. The phrasing 'A group's members: 1 call.' is slightly fragmentary but remains efficient and clear.

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 fully explains the return values and includes the important non-member edge case. Safety is covered by annotations, and usage is clear. An agent has everything needed to call and interpret this tool correctly.

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%, so the input schema fully documents limit, offset, and group_id. The description adds no parameter-specific syntax or meaning beyond what the schema provides, which is appropriate given the high coverage. Baseline 3 is correct.

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 description states a specific verb and resource: 'A group's members: 1 call.' It also distinguishes from the sibling manage_memberships by instructing use 'ALWAYS before manage_memberships with remove_absent.' An agent can immediately tell this is a read-only listing tool for group members.

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?

It gives clear usage context: 'Use it to resolve a name to a user_id and ALWAYS before manage_memberships with remove_absent.' It also warns that a non-member gets an empty list, not 403, which is a key usage nuance. It lacks explicit when-not-to-use guidance, but the context is strong.

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