Skip to main content
Glama
saucelabs

Sauce Labs MCP Server

Official
by saucelabs

lookup_service_accounts

Lists existing service accounts in your Sauce Labs organization with optional filters by ID, username, teams, and pagination.

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
linksYes
countYes
resultsYes
Behavior3/5

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

No annotations provided, so description must carry burden. It implies read-only by stating 'lists', but doesn't explicitly confirm no side effects, rate limits, or permission requirements. Pagination is hinted via limit/offset parameters.

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 front-loaded with the main purpose and then lists parameters. It is not overly long but includes some redundancy in parameter descriptions. Could be tightened slightly.

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 the output schema exists and no nested objects, the description adequately covers the tool's behavior. It explains filtering options and pagination, but could mention the scope ('existing service accounts') more explicitly as organization-wide.

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

Parameters4/5

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

Schema description coverage is 0%, but the description compensates by explaining each parameter's purpose and format (e.g., 'Comma-separated service account IDs', 'usernames that begin with the specified value'). However, the id description is slightly redundant.

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 clearly states 'Lists existing service accounts in your organization' which is a specific verb+resource. It also mentions filtering via query parameters, distinguishing it from sibling tools like get_service_account which retrieves a single account.

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?

No guidance on when to use this tool versus alternatives. Siblings like get_service_account and lookup_users exist but no comparison or exclusion criteria are 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