Skip to main content
Glama
saucelabs

Sauce Labs MCP Server

Official
by saucelabs

get_specific_real_device_job_asset

Download specific test assets like logs, videos, or crash reports from mobile app testing jobs run on physical devices in Sauce Labs Real Device Cloud.

Instructions

    Download a specific asset for a Real Device Cloud (RDC) job.

    USE THIS METHOD WHEN:
    - The job ran on a physical mobile device (iPhone, Android, etc.)
    - get_test_assets returns an error about "Real Device job"
    - get_log_json_file fails with asset not found errors
    - You need logs/videos from mobile app testing

    For web browser testing on virtual machines, use get_test_assets instead.

    :param job_id: Required. The unique identifier of a job running on a real device in the data center. You can look up job
        IDs using the Get Real Device Jobs endpoint.
    :param asset_type: Required. The unique identifier of a job running on a real device in the data center. You can look up job
        IDs using the Get Real Device Jobs endpoint. Possible values are:

        'deviceLogs' - Device Logs | Appium, Espresso, XCUITest
        'appiumLogs' - Appium Logs | Appium
        'appiumRequests' - Appium Requests | Appium
        'junit.xml' - JUnit XML | Espresso, XCUITest
        'xcuitestLogs' - XCUITest Logs | XCUITest
        'video.mp4' - Video | Appium, Espresso, XCUITest
        'screenshots.zip' - Screenshots | Appium, Espresso
        'network.har' - Network Logs | Appium, Espresso, XCUITest
        'insights.json' - Device Vitals | Appium, Espresso, XCUITest
        'crash.json' - Crash Logs | Appium
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYes
asset_typeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by specifying this is for downloading assets from real device jobs, mentioning error scenarios, and listing specific asset types. It doesn't cover rate limits, authentication needs, or file size considerations, but provides substantial operational context.

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 well-structured with clear sections (purpose, usage guidelines, parameters) and uses bullet points effectively. While comprehensive, it maintains focus with minimal wasted text, though the parameter documentation is quite detailed.

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

Completeness5/5

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

Given the tool's complexity (2 parameters with 0% schema coverage, no annotations), the description provides complete context: clear purpose, detailed usage guidelines, comprehensive parameter documentation, and sibling tool differentiation. The existence of an output schema means return values don't need explanation.

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?

With 0% schema description coverage, the description fully compensates by providing detailed parameter documentation. It explains both parameters thoroughly: job_id's purpose and how to obtain it, and asset_type with comprehensive enum values and their associated frameworks. 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 specific action ('Download a specific asset') and resource ('for a Real Device Cloud job'), distinguishing it from sibling tools like 'get_test_assets' for web browser testing. It explicitly identifies the target as physical mobile device assets, providing precise differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit 'USE THIS METHOD WHEN' criteria with four specific scenarios, plus a clear alternative ('For web browser testing on virtual machines, use get_test_assets instead'). This gives comprehensive guidance on when to use this tool versus alternatives.

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