Skip to main content
Glama
saucelabs

Sauce Labs MCP Server

Official
by saucelabs

lookup_service_accounts

List and filter service accounts in your Sauce Labs organization by ID, username, or team membership to manage access and permissions.

Instructions

    Lists existing service accounts in your organization. You can filter the results using the query parameters below.
    :param id: Optional. Comma-separated service account 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 service accounts in the organization with usernames beginning with "an".
    :param teams: Optional. Limit results to service account who belong to the specified team_ids. Specify multiple
        teams as comma-separated values.
    :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
limitNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
linksYes
resultsYes
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a list operation, implying read-only behavior, but doesn't disclose authentication requirements, rate limits, pagination details beyond limit/offset, or what the output contains. The description adds minimal behavioral context beyond the basic list functionality.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is appropriately sized but not optimally structured. The first sentence states the purpose, followed by parameter documentation. However, the parameter explanations are somewhat verbose (e.g., the username example is helpful but lengthy). It could be more front-loaded with key usage information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 5 parameters with 0% schema coverage and no annotations, the description does well on parameters but lacks other context. Since an output schema exists, the description doesn't need to explain return values. However, for a list tool with filtering, it should mention more about behavioral aspects like pagination behavior or result ordering.

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 fully. It provides detailed semantic explanations for all 5 parameters: 'id' (comma-separated IDs), 'username' (prefix matching with example), 'teams' (comma-separated team_ids), 'limit' (max per page with default 20), and 'offset' (starting record). This adds significant value 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's purpose: 'Lists existing service accounts in your organization.' It specifies the resource (service accounts) and action (list), though it doesn't explicitly differentiate from sibling tools like 'get_service_account' or 'lookup_users' which might have overlapping functionality. The purpose is specific but lacks sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. It mentions filtering capabilities but doesn't compare to sibling tools like 'get_service_account' (singular) or 'lookup_users' (different resource). There's no mention of prerequisites, context, or exclusions for usage.

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