Skip to main content
Glama

parabol

by io.usefulapi

List organization users

list_organization_users
Read-only

List the users in an organization (Relay connection): each org-user's role, joinedAt, tier, and underlying user (preferredName, email). Paginate with first + after (pass the last edge's cursor). Parabol GraphQL: viewer.organization(orgId).organizationUsers. Requires ORGS_READ + USERS_READ.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoCursor for the next page (the `cursor` of the last edge from a prior call).
firstNoMax org-users to return (page size).
orgIdYesThe organization id.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses the Relay connection format, the exact data shape, pagination cursor behavior, the underlying GraphQL query path, and permission requirements. This gives an agent meaningful behavioral expectations before invoking the tool.

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?

Two well-structured sentences deliver the core purpose, returned fields, pagination method, GraphQL source, and permission requirements with no filler. The most important information is front-loaded.

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?

All three parameters are thoroughly documented in the schema, and the description adds the return field list and pagination contract despite there being no output schema. Combined with permission and GraphQL path context, an agent has everything needed to call the 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 coverage is 100%, so the schema already fully documents orgId, first, and after. The description reinforces pagination with first + after and clarifies the cursor usage, but this largely mirrors the schema and adds little new semantic value beyond what structured definitions already provide.

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 uses a specific verb ('List'), identifies the resource ('users in an organization'), and enumerates the returned fields (role, joinedAt, tier, preferredName, email). This clearly distinguishes it from sibling tools like list_team_members and list_organizations without ambiguity.

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?

The description provides clear context for use, including pagination mechanics and required permissions (ORGS_READ + USERS_READ). It does not explicitly name alternatives or state when not to use this tool, but the org vs. team distinction among siblings is implicit and sufficient.

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

All parabol toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Every tool targets a distinct resource and action: get_/list_ tools are clearly separate read paths, create_/update_/start_/add_ tools map to distinct mutations, and the two escape hatches are explicitly labeled. Even near neighbors like list_meetings and list_active_meetings are unambiguous.

Naming Consistency4/5

Most tools follow a consistent pattern: list_/get_ for reads, create_/update_/start_ for mutations, with plural nouns for collections and singular for single resources. Minor deviations like add_comment, invite_to_team, and the parabol_* escape hatches prevent a perfect score.

Tool Count3/5

With 21 tools, the server sits in the 16-25 range that feels heavy for an MCP surface. The breadth is somewhat justified because Parabol spans organizations, teams, meetings, tasks, and comments, but many tools are list/get variants of the same core entities.

Completeness3/5

Core read and write flows exist for teams, organizations, meetings, tasks, and comments, but there are notable lifecycle gaps such as no delete_task, no reflection update/delete, and no meeting end/update mutations. The parabol_graphql and parabol_query escape hatches help work around these gaps but do not make the curated surface fully complete.

Resources