Skip to main content
Glama
saucelabs

Sauce Labs MCP Server

Official
by saucelabs

lookup_teams

Query teams in your Sauce Labs organization by ID or name to retrieve team summaries and IDs.

Instructions

    Queries the organization of the requesting account and returns the number of teams matching the query and a
    summary of each team, including the ID value, which may be a required parameter of other API calls related
    to a specific team.You can filter the results of your query using the name parameter below.
    :param id: Optional. Comma-separated team IDs. Allows to receive details of multiple teams at once. For example,
        id=3d60780314724ab8ac688b50aadd9ff9,f9acc7c5b1da4fd0902b184c4f0b6324 would return details of teams with IDs
        included in the provided list.
    :param name: Optional. Returns the set of teams that begin with the specified name value. For example, name=sauce would
        return all teams in the organization with names beginning with "sauce".
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description should convey behavioral traits. However, it only describes querying and returning data, with no mention of side effects, authentication needs, rate limits, or performance constraints. It assumes a read-only operation but does not explicitly state that.

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 structured with a general purpose overview followed by parameter details in a docstring format. It is not excessively long, but the pseudo-docstring could be more concise.

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 no annotations, the description covers the tool's purpose, filtering options, and that it returns team summaries including IDs. It provides enough context for an agent to use the tool correctly, though it omits details like pagination or limits.

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%, yet the description thoroughly explains both parameters: 'id' as comma-separated IDs for multiple teams, and 'name' as a prefix filter. This adds essential meaning that the schema lacks.

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 that the tool queries the organization and returns the number and summary of matching teams, including IDs. It distinguishes from siblings like 'get_team' by implying it returns multiple teams with filtering, but does not explicitly contrast.

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 explains filtering by name and id, which implies when to use the tool (e.g., looking for teams by name prefix or specific IDs), but it lacks explicit guidance on when not to use it or direct comparisons with sibling tools like 'get_team'.

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