Mencoro

List organization members

list_members

Read-onlyIdempotent

The members of an organization, oldest first, with their role and state; optionally also its pending invitations. Owners only, as in the web app. The member "id" (not the userId) is what change_member_role, suspend_member and reactivate_member take.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`organizationId`	Yes
`includeInvitations`	No

Output Schema

Name	Required	Description	Default
`members`	Yes
`pendingInvitations`	Yes	Null unless includeInvitations was true. Every pending invitation, oldest first, up to 100.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedOutput schema / properties / pendingInvitations / anyOf

Previous value: -[
-  {
-    "properties": {
-      "items": {
-        "items": {
-          "description": "An invitation to join an organization",
-          "properties": {
-            "acceptedAt": {
-              "format": "date-time",
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "createdAt": {
-              "format": "date-time",
-              "type": "string"
-            },
-            "email": {
-              "format": "email",
-              "type": "string"
-            },
-            "expiresAt": {
-              "format": "date-time",
-              "type": "string"
-            },
-            "id": {
-              "format": "uuid",
-              "type": "string"
-            },
-            "role": {
-              "enum": [
-                "owner",
-                "manager",
-                "viewer"
-              ],
-              "type": "string"
-            },
-            "state": {
-              "enum": [
-                "pending",
-                "accepted",
-                "rejected",
-                "expired",
-                "cancelled"
-              ],
-              "type": "string"
-            }
-          },
-          "required": [
-            "id",
-            "email",
-            "role",
-            "state",
-            "createdAt",
-            "expiresAt"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "total": {
-        "type": "integer"
-      }
-    },
-    "required": [
-      "items",
-      "total"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "items": {
+        "items": {
+          "description": "An invitation to join an organization",
+          "properties": {
+            "acceptedAt": {
+              "format": "date-time",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "createdAt": {
+              "format": "date-time",
+              "type": "string"
+            },
+            "email": {
+              "format": "email",
+              "type": "string"
+            },
+            "expiresAt": {
+              "format": "date-time",
+              "type": "string"
+            },
+            "id": {
+              "format": "uuid",
+              "type": "string"
+            },
+            "projectAccessMode": {
+              "description": "Which projects of the organization the invitee reaches on accepting: every project, or only projectIds",
+              "enum": [
+                "all",
+                "selected"
+              ],
+              "type": "string"
+            },
+            "projectIds": {
+              "description": "The projects a selected access reaches, limited to those still in the organization; empty when the mode is all. It may be empty on selected once its projects left the organization, which grants nothing",
+              "items": {
+                "format": "uuid",
+                "type": "string"
+              },
+              "type": "array"
+            },
+            "role": {
+              "enum": [
+                "owner",
+                "manager",
+                "viewer"
+              ],
+              "type": "string"
+            },
+            "state": {
+              "enum": [
+                "pending",
+                "accepted",
+                "rejected",
+                "expired",
+                "cancelled"
+              ],
+              "type": "string"
+            }
+          },
+          "required": [
+            "id",
+            "email",
+            "role",
+            "state",
+            "createdAt",
+            "expiresAt",
+            "projectAccessMode",
+            "projectIds"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "total": {
+        "type": "integer"
+      }
+    },
+    "required": [
+      "items",
+      "total"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed3 schema fields changedOct 29, 2026

addedOutput schema / properties / members / properties / items / items / properties / projectAccessMode

Added value: +{
+  "description": "Which projects of the organization the member reaches: every project, or only projectIds",
+  "enum": [
+    "all",
+    "selected"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / members / properties / items / items / properties / projectIds

Added value: +{
+  "description": "The projects a selected access reaches; empty when the mode is all",
+  "items": {
+    "format": "uuid",
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / members / properties / items / items / required

Previous value: -[
-  "id",
-  "userId",
-  "role",
-  "state",
-  "isActive",
-  "joinedAt"
-]New value: +[
+  "id",
+  "userId",
+  "role",
+  "state",
+  "isActive",
+  "joinedAt",
+  "projectAccessMode",
+  "projectIds"
+]

AddedSep 28, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish the safe read-only, idempotent, non-destructive profile. The description adds meaningful behavioral context beyond annotations: owners-only access, oldest-first ordering, role and state in results, optional invitation inclusion, and the distinction between member id and userId.

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

Conciseness5/5

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

The description is three dense sentences that are front-loaded with the core purpose and constraint. There is no filler, and the id note is placed after the main listing behavior.

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?

Output schema exists, so return values need not be fully explained, and annotations cover safety. However, with zero schema parameter descriptions, the missing explanation of limit and offset leaves the definition incomplete for correct pagination.

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%, so the description must compensate for all four parameters. It explains includeInvitations and implicitly organizationId, but says nothing about limit or offset, leaving half the parameters undocumented.

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: it lists organization members, including ordering, returned fields, and optional pending invitations. It also distinguishes the member id from userId and names the sibling mutation tools that consume that id.

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 a clear usage constraint: owners only, matching the web app. It also signals when to use the optional invitation behavior via 'optionally also its pending invitations.' It does not explicitly compare against every sibling, but the scope is clear.

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

All Mencoro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.