Skip to main content
Glama
saucelabs

Sauce Labs MCP Server

Official
by saucelabs

lookup_users

Search and filter users in your Sauce Labs organization by ID, username, team, role, or status to manage access and identify specific accounts.

Instructions

    Queries the organization of the requesting account and returns the number of users matching the query and a basic
    profile of each user, including the ID value, which may be a required parameter of other API calls related to a
    specific user. You can narrow the results of your query using any of the following filtering parameters.
    :param id: Optional. Comma-separated user IDs. Allows to receive details of multiple user at once. For example,
        id=3d60780314724ab8ac688b50aadd9ff9,f9acc7c5b1da4fd0902b184c4f0b6324 would return details of users with IDs
        included in the provided list.
    :param username: Optional. Limits the results to usernames that begin with the specified value. For example,
        username=an would return all users in the organization with usernames beginning with "an".
    :param teams: Optional. Limit results to users who belong to the specified team_ids. Specify multiple teams as
        comma-separated values.
    :param roles: Optional. Limit results to users who are assigned certain roles. Valid values are: 1 - Organization Admin,
        4 - Team Admin, 3 - Member. Specify multiple roles as comma-separated values.
    :param phrase: Optional. Limit results to users whose first name, last name, or email address begins with the specified value.
    :param status: Optional. Limit results to users of the specifid status. Valid values are: 'active', 'pending', 'inactive'
    :param limit: Optional. Limit results to a maximum number per page. Default value is 20.
    :param offset: Optional. The starting record number from which to return results.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
usernameNo
teamsNo
rolesNo
phraseNo
statusNo
limitNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
linksYes
resultsYes
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the tool queries the organization of the requesting account (scope), returns count and basic profiles, and mentions pagination behavior via limit/offset with a default limit of 20. However, it doesn't cover rate limits, authentication requirements, error conditions, or whether it's read-only/destructive—leaving significant behavioral gaps.

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?

The description is appropriately sized and front-loaded: the first sentence states core purpose, the second adds context about ID usefulness, and the third introduces filtering parameters before detailing each. While slightly verbose due to parameter explanations, every sentence earns its place by providing essential information not in the schema.

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?

Given 8 parameters with 0% schema coverage and no annotations, the description does heavy lifting: explains all parameters thoroughly and mentions output includes count and basic profiles. With an output schema present (per context signals), return values needn't be detailed. However, it lacks information on authentication, error handling, and rate limits, leaving some gaps for a query tool.

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 0%, so the description must compensate—and it does excellently. For all 8 parameters, it provides clear semantics: purpose (e.g., 'limits results to usernames that begin with'), format (comma-separated values), examples, valid values for enums (roles, status), and defaults (limit=20). This adds substantial meaning beyond the bare schema.

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 clearly states the tool 'queries the organization' and 'returns the number of users matching the query and a basic profile of each user', providing specific verb (queries/returns) and resource (users). It distinguishes from siblings like 'get_user' by indicating it returns multiple users with filtering capabilities, though not explicitly contrasting with 'list_team_members' or other user-related tools.

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?

The description implies usage for querying multiple users with filtering, mentioning the ID value may be required for other API calls, but lacks explicit guidance on when to use this versus alternatives like 'get_user' (single user) or 'list_team_members' (team-specific). No when-not-to-use or prerequisite information is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/saucelabs/sauce-api-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server