Sauce Labs MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

lookup_service_accounts

List and filter existing service accounts in your organization by ID, username, or team, with pagination controls for managing access.

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

Name	Required	Description	Default
`id`	No
`limit`	No
`teams`	No
`offset`	No
`username`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv1.3.0Oct 25, 2026

addedOutput schema / $defs / ErrorResponse

Added value: +{
+  "properties": {
+    "error": {
+      "title": "Error",
+      "type": "string"
+    }
+  },
+  "required": [
+    "error"
+  ],
+  "title": "ErrorResponse",
+  "type": "object"
+}

addedOutput schema / $defs / LookupServiceAccounts

Added value: +{
+  "properties": {
+    "count": {
+      "title": "Count",
+      "type": "integer"
+    },
+    "links": {
+      "$ref": "#/$defs/LookupUsersLinks"
+    },
+    "results": {
+      "items": {
+        "$ref": "#/$defs/ServiceAccount"
+      },
+      "title": "Results",
+      "type": "array"
+    }
+  },
+  "required": [
+    "links",
+    "count",
+    "results"
+  ],
+  "title": "LookupServiceAccounts",
+  "type": "object"
+}

removedOutput schema / properties / count

Removed value: -{
-  "title": "Count",
-  "type": "integer"
-}

removedOutput schema / properties / links

Removed value: -{
-  "$ref": "#/$defs/LookupUsersLinks"
-}

addedOutput schema / properties / result

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/LookupServiceAccounts"
+    },
+    {
+      "$ref": "#/$defs/ErrorResponse"
+    }
+  ],
+  "title": "Result"
+}

removedOutput schema / properties / results

Removed value: -{
-  "items": {
-    "$ref": "#/$defs/ServiceAccount"
-  },
-  "title": "Results",
-  "type": "array"
-}

changedOutput schema / required

Previous value: -[
-  "links",
-  "count",
-  "results"
-]New value: +[
+  "result"
+]

changedOutput schema / title

Previous value: -"LookupServiceAccounts"New value: +"lookup_service_accountsOutput"

First observedJan 23, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses pagination behavior and the default limit of 20, plus prefix matching and comma-separated filter semantics, but it does not state read-only status, required permissions, organization scoping behavior, or any rate limits.

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 first sentence front-loads the tool purpose, followed by a structured parameter list that is useful given the schema’s lack of descriptions. It is somewhat verbose and includes a minor grammatical fragment in the id explanation, but no sentence is broadly wasteful.

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?

An output schema exists, so return values need not be documented in the description. The parameters are fully described despite zero schema coverage, but the description still lacks explicit routing guidance against sibling lookup tools and does not clarify authorization or scope requirements.

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 document all five parameters, and it does: id as comma-separated IDs, username as prefix matching, teams as comma-separated team_ids, limit with a default of 20, and offset as the starting record. This fully compensates for 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 uses a specific verb and resource: "Lists existing service accounts in your organization." This clearly identifies a list/lookup operation, though it does not explicitly distinguish it from the sibling get_service_account tool.

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?

It explains that query parameters can filter results and gives useful examples for username and teams. However, it does not say when to use this tool versus get_service_account, lookup_users, or lookup_teams, nor does it provide exclusions or prerequisites.

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