Skip to main content
Glama

List user organization memberships

list_user_organization_memberships
Read-onlyIdempotent

List the organizations a user belongs to, including their role and permissions in each. Returns newest memberships first with offset pagination and a total count. The user must belong to the selected application instance. Organization and membership 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>",
      "user_id": "<user_id>"
    },
    "name": "list_user_organization_memberships"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum memberships to return (default 10).
offsetNoMemberships to skip (default 0).
user_idYesID of the user in the selected instance.
instanceYesInstance to target: "development", "production", or a full instance ID (ins_…).
application_idYesClerk application ID (app_…).

Output Schema

NameRequiredDescriptionDefault
dataYes
total_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, closed-world operation, and the description adds real context beyond them: 'newest memberships first,' offset-pagination semantics with a total count, and the guarantee that 'Organization and membership private metadata are never returned' (a data-exclusion promise an agent could not infer otherwise). It does not cover error behavior when the prerequisite fails or any rate limits, which keeps it below a 5.

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?

Four short sentences, each carrying distinct information: purpose, ordering/pagination, precondition, and privacy exclusion. Nothing is repeated from the schema or the annotations, and the core purpose is front-loaded in the first clause.

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 an output schema present, the description need not describe return values, and it does not waste space doing so. Combined with 100% parameter coverage and explicit safety annotations, the remaining behavioral facts an agent needs (ordering, pagination, prerequisite, excluded data) are all stated.

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

Parameters5/5

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

Schema description coverage is 100%, so the schema already defines limit, offset, user_id, instance, and application_id with defaults and bounds. The description mentions offset pagination and total count, which is consistent with the schema but adds no new syntax or format detail, so the baseline score of 3 would apply absent other factors. I raise it to 5 because the schema is fully self-documenting and the description correctly avoids duplicating it, but the parameter guidance itself is baseline-level.

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 opens with a specific verb and resource plus the traversal direction: 'List the organizations a user belongs to,' which is the inverse of the sibling list_organization_memberships (members of an organization). It also states what each record carries ('role and permissions in each'), so an agent can distinguish it from the other list tools without opening the schema.

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 precondition that selects this tool in practice: 'The user must belong to the selected application instance,' which also tells the agent the required application_id/instance/user_id triple is meaningful. It stops short of naming an alternative tool or an explicit when-not-to-use condition, so it is clear context rather than a full routing rule.

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