Skip to main content
Glama

List organizations

list_organizations
Read-onlyIdempotent

List or search organizations in an application instance, with pagination and a total count. Filters match the Backend API organization list. Private metadata is 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>"
    },
    "name": "list_organizations"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFilter by organization name.
slugNoFilter by organization slug.
limitNoMaximum organizations to return (default 10).
queryNoExact organization ID, or partial name or slug.
offsetNoOrganizations to skip before returning results.
user_idNoFilter by member user IDs; prefix an ID with - to exclude it.
instanceYesInstance to target: "development", "production", or a full instance ID (ins_…).
order_byNoSort by name, created_at, updated_at, last_active_at, or members_count. Prefix with - for descending (default -created_at).
filter_byNoChoose one filter. The missing-member filter requires include_missing_member_with_elevated_permissions=true.
application_idYesClerk application ID (app_…).
organization_idNoOrganization IDs to include; prefix an ID with - to exclude it.
created_at_afterNoCreation lower bound as a Unix timestamp in milliseconds.
created_at_beforeNoCreation cutoff as a Unix timestamp in milliseconds.
include_members_countNoInclude each organization's member count.
include_missing_member_with_elevated_permissionsNoInclude whether each organization lacks a member with elevated permissions.

Output Schema

NameRequiredDescriptionDefault
dataYes
total_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description is not carrying the safety burden. It still adds genuine value beyond that: results are paginated, a total count is produced, and private metadata is explicitly excluded from the response. It does not mention rate limits or auth scope, which keeps it from 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.

Conciseness4/5

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

Three short sentences, front-loaded with the core action, with the data-exposure caveat placed last where it belongs. Every sentence carries information; the only soft spot is the vague "Filters match the Backend API organization list" reference.

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?

For a 15-parameter list tool, the description covers purpose, pagination, total count, and a data-privacy boundary, while the schema documents every parameter and an output schema exists so return shape need not be explained. What is missing is interaction guidance among filters (e.g. query vs name/slug) and the required-parameter implication, but the structured fields compensate.

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 every one of the 15 parameters (limit, offset, order_by, filter_by, user_id, query, etc.) is already documented in the schema. The description adds no parameter-level meaning beyond the pointer to the Backend API filter semantics, so the baseline 3 applies.

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?

"List or search organizations in an application instance" names a concrete verb and resource and implies the scope (per-instance). It does not explicitly distinguish itself from siblings like list_organization_memberships or list_users, so it stops short of a 5, but an agent can still identify what this tool returns.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites such as needing an application_id plus instance, and no routing to alternatives (e.g. membership listing). The only directional hint is "Filters match the Backend API organization list," which points to external documentation rather than stating usage rules.

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