Skip to main content
Glama
saucelabs

Sauce Labs MCP Server

Official
by saucelabs

lookup_jobs_in_build

Retrieve jobs associated with a build, using optional filters like status or completion to narrow results.

Instructions

    Returns information about all jobs associated with the specified build. You can limit which jobs are
    returned using any of the optional filtering parameters.
    :param build_source: Required. The type of test device associated with the build and its jobs. Valid values are:
        rdc - Real Device Builds, vdc - Emulator or Simulator Builds
    :param build_id: Required. The unique identifier of the build whose jobs you are looking up. You can look up
        build IDs in your organization using the Lookup Builds endpoint.
    :param modified_since: Optional. Returns only jobs that have been modified after this unicode timestamp.
    :param completed: Optional. Returns jobs based on whether they completed, meaning the tests ran uninterrupted to
        completion: true - Return jobs that have a completed state of true, false - Return jobs that have a
        completed state of false.
    :param errored: Optional. Returns jobs based on their errored state: true - Return jobs that have an errored
        state of true, false - Return jobs that have an errored state of false.
    :param failed: Optional. Returns jobs based on their failed state: true - Return jobs that have a failed state
        of true, false - Return jobs that have a failed state of false.
    :param finished: Optional. Returns jobs based on whether they have finished, meaning they are no longer
        running, but may not have run to completion: true - Return jobs that have a finished state of true, false -
        Return jobs that have a finished state of false.
    :param new: Optional. Returns jobs based on their new state: true - Return jobs that have a new state of true,
        false - Return jobs that have a new state of false.
    :param passed: Optional. Returns jobs based on their passed state: true - Return jobs that have a passed state
        of true, false - Return jobs that have a passed state of false.
    :param public: Optional. Returns jobs based on whether they were run on public devices: true - Return jobs that
        have a public state of true, false - Return jobs that have a public state of false.
    :param queued: Optional. Returns jobs based on whether their current state is queued: true - Return jobs that
        have a queued state of true, false - Return jobs that have a queued state of false.
    :param running: Optional. Returns jobs based on whether they are currently in a running state: true - Return
        jobs that are currently running, false - Return jobs that are not currently running.
    :param faulty: Optional. Returns jobs based on whether they are identified as faulty, meaning either errored or
        failed state is true. true - Return jobs that have a faulty state of true, false - Return jobs that have a
        faulty state of false.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
build_sourceYes
build_idYes
modified_sinceNo
completedNo
erroredNo
failedNo
finishedNo
newNo
passedNo
publicNo
queuedNo
runningNo
faultyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description should disclose behavioral traits, but it only lists parameters. It does not mention what happens if the build is missing, rate limits, pagination, or ordering of results. The agent lacks crucial runtime context.

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 a block of text with parameter listings; it is functional but not concisely front-loaded. The first sentence states the purpose, but the parameter list is verbose and could be more structured (e.g., grouping filter parameters).

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 13 parameters and no annotations, the description covers all parameter semantics but lacks broader context: no mention of output structure, error handling, or limits. The existence of an output schema helps but is not referenced.

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?

Since schema_description_coverage is 0%, the description compensates by explaining each parameter's purpose and valid values (e.g., build_source lists 'rdc' and 'vdc', boolean filters clarify true/false meaning). 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns information about jobs for a specified build, using the verb 'Returns' and specifying the resource 'jobs associated with the specified build'. This distinguishes it from sibling tools like get_build (build info) and get_job_details (single job).

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 explicit guidance on when to use this tool versus alternatives. It does not state what scenarios warrant filtering or when other endpoints (e.g., get_recent_jobs) might be more appropriate.

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