Skip to main content
Glama

List organization memberships

list_organization_memberships
Read-onlyIdempotent

List an organization's members with their roles, permissions, and public user identity in an application instance. Supports Backend API membership filters, pagination, and a total count. Membership and organization private metadata are never returned.

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": {
      "application_id": "<application_id>",
      "instance": "<instance>",
      "organization_id": "<organization_id>"
    },
    "name": "list_organization_memberships"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoFilter by role keys, such as org:admin or org:member.
limitNoMaximum memberships to return (default 10).
queryNoPartial match across user identity fields.
offsetNoMemberships to skip before returning results.
user_idNoFilter by literal user IDs. Prefixes are not interpreted as include/exclude operators.
instanceYesInstance to target: "development", "production", or a full instance ID (ins_…).
order_byNoSort by created_at, email_address, phone_number, first_name, last_name, username, or role. Prefix with - for descending.
usernameNoFilter by exact usernames.
name_queryNoCase-insensitive partial name match.
web3_walletNoFilter by exact web3 wallet addresses.
phone_numberNoFilter by exact phone numbers.
email_addressNoFilter by exact email addresses.
application_idYesClerk application ID (app_…).
username_queryNoCase-insensitive partial username match.
organization_idYesOrganization whose members to list.
created_at_afterNoUser creation lower bound as a Unix timestamp in milliseconds.
created_at_beforeNoUser creation cutoff as a Unix timestamp in milliseconds.
phone_number_queryNoPartial phone number match.
email_address_queryNoCase-insensitive partial email address match.
last_active_at_afterNoUser activity lower bound as a Unix timestamp in milliseconds.
last_active_at_beforeNoUser activity cutoff as a Unix timestamp in milliseconds.

Output Schema

NameRequiredDescriptionDefault
dataYes
total_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world scope, so the safety profile is covered. The description adds genuinely non-derived context: membership and organization private metadata are never returned, and results include a total count alongside paginated rows. It still omits auth/permission prerequisites and any rate-limit behavior.

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?

Three short sentences with the core purpose front-loaded and no repetition of the title. The phrase "Supports Backend API membership filters" is slightly vague filler, but the closing exclusion sentence earns its place by preventing wasted parsing of absent metadata.

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?

With 21 parameters fully covered by schema descriptions and an output schema present, the description does not need to restate arguments or return shapes. Naming the excluded metadata and confirming the total count fills the remaining informational gaps; only permission prerequisites are left unstated for a read-only listing tool.

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% across all 21 parameters, so the schema documents role filters, cursor-style limit/offset, query variants, ordering, and timestamp bounds. The description only summarizes this generically as "Backend API membership filters, pagination, and a total count" without adding syntax or edge-case guidance, which is the expected baseline when the schema carries the load.

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 opens with a specific verb+resource and scope: "List an organization's members with their roles, permissions, and public user identity in an application instance." That is more precise than the name alone because it enumerates returned fields and names the application-instance context. It does not explicitly contrast with the reversed sibling list_user_organization_memberships, so it stops short of a 5.

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 implied by the directional framing (organization -> members), but there is no explicit when-to-use statement, no exclusions, and no pointer to list_user_organization_memberships for the inverse lookup. The mention of supported filters, pagination, and total count tells the agent what the tool can do but not when to prefer it.

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.

Resources