Skip to main content
Glama
saucelabs

Sauce Labs MCP Server

Official
by saucelabs

update_storage_group_settings

Update app storage group configurations by specifying group ID and optional settings like proxy, audio capture, language, orientation, resigning, or instrumentation to customize your test environment.

Instructions

    Update app storage group settings for the specified group.

    :param group_id: Required. The unique identifier of the app group.
    :param proxy: Optional. Proxy configuration with 'host' and 'port' keys.
    :param audio_capture: Optional. Enable/disable audio capture during testing.
    :param proxy_enabled: Optional. Enable/disable proxy usage.
    :param lang: Optional. Language setting (e.g., 'en_GB', 'en_US').
    :param orientation: Optional. Device orientation preference.
    :param resigning_enabled: Optional. Enable/disable app resigning (iOS only).
    :param resigning: Optional. iOS-specific resigning settings dict with keys:
        - image_injection: bool
        - group_directory: bool
        - biometrics: bool
        - sys_alerts_delay: bool
        - network_capture: bool
        - vitals: bool (seen in other examples)
        - backtrace: bool (seen in other examples)
    :param instrumentation: Optional. Android-specific instrumentation settings.
    :return: Updated settings response from API.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYes
proxyNo
audio_captureNo
proxy_enabledNo
langNo
orientationNo
resigning_enabledNo
resigningNo
instrumentationNo

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, and the description does not disclose any behavioral traits such as whether the update is idempotent, destructive, or requires specific permissions. It only states that it updates settings.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose, listing all parameters with types, which could be more concise. The initial sentence is clear, but the parameter dump is not streamlined.

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 the tool has 9 parameters and no schema descriptions, the description covers them well. However, it lacks overall context about the update behavior (e.g., merge vs replace) and only vaguely mentions the return value.

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?

The schema has 0% description coverage, and the description compensates by explaining each parameter in detail, including nested structures like resigning settings. This adds significant value beyond the 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 'Update app storage group settings' with a specific verb and resource, and distinguishes itself from sibling tools like get_storage_groups_settings.

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 is given on when to use this tool versus alternatives. For example, it does not mention that get_storage_groups_settings should be used to view current settings.

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