Skip to main content
Glama
saucelabs

Sauce Labs MCP Server

Official
by saucelabs

update_storage_group_settings

Modify app storage group configurations including proxy settings, audio capture, device orientation, language preferences, and platform-specific options for iOS resigning or Android instrumentation to optimize testing environments.

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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is an update operation but doesn't mention whether it's idempotent, what permissions are required, whether changes are reversible, or any rate limits. The return statement is generic and doesn't describe error conditions or response format.

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 appropriately sized and well-structured with a clear opening sentence followed by parameter documentation. While comprehensive, every sentence adds value by explaining parameters that aren't documented in the schema. The parameter explanations could be slightly more concise but are necessary given the schema coverage gap.

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 the tool's complexity (9 parameters, mutation operation) and the presence of an output schema (which handles return values), the description is reasonably complete. It thoroughly documents all parameters and their semantics. However, it lacks behavioral context about permissions, side effects, and error handling that would be important for a mutation tool with no annotations.

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 description provides excellent parameter semantics beyond the schema, which has 0% description coverage. It explains each parameter's purpose, required/optional status, and provides specific examples (e.g., 'en_GB', 'en_US' for lang) and detailed sub-keys for the 'resigning' parameter. This fully compensates for the schema's lack of descriptions.

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 the verb ('Update') and resource ('app storage group settings for the specified group'), making the purpose unambiguous. However, it doesn't explicitly differentiate this tool from sibling tools like 'get_storage_groups_settings', which appears to retrieve rather than update 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 guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., permissions needed), when not to use it, or how it relates to sibling tools like 'get_storage_groups_settings' for retrieval.

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