Skip to main content
Glama
saucelabs

Sauce Labs MCP Server

Official
by saucelabs

get_network_har_file

Retrieves and filters HAR data from a Sauce Labs test job. Use predefined categories for common patterns or custom filters for detailed control.

Instructions

    Retrieves and filters HAR file data from a Sauce Labs test job.

    The tool can intelligently filter requests to reduce data size and focus analysis.
    Use filter categories for common patterns, or specify custom filters for detailed control.

    :param job_id: The Sauce Labs Job ID (works for VDC jobs with network capture enabled)
    :param filter_category: Predefined filter categories:
        - "analytics" - Google Analytics, Facebook Pixel, Adobe Analytics, Comscore, etc.
        - "api" - Internal API calls (same domain as main site, JSON responses)
        - "fonts" - Font loading requests (woff, woff2, ttf, etc.)
        - "images" - Image resources (jpg, png, webp, svg, etc.)
        - "scripts" - JavaScript files and external scripts
        - "errors" - Failed requests (4xx, 5xx status codes)
        - "slow" - Requests taking longer than 1 second
        - "third-party" - All external domain requests
    :param custom_domains: List of domain patterns to include (e.g., ["google", "facebook", "api.company.com"])
    :param resource_types: List of resource types to include (e.g., ["Script", "XHR", "Image"])
    :param status_codes: List of HTTP status codes to include (e.g., [200, 404, 500])
    :return: Filtered HAR data structure with only matching requests

    Examples:
    - get_network_har_file(job_id, filter_category="analytics")
    - get_network_har_file(job_id, filter_category="api")
    - get_network_har_file(job_id, custom_domains=["retailmenot.com"], resource_types=["XHR"])
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYes
filter_categoryNo
custom_domainsNo
resource_typesNo
status_codesNo
Behavior3/5

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

No annotations provided, so description carries full burden. Notes constraint: 'works for VDC jobs with network capture enabled', but does not disclose rate limits, authentication needs, or error handling behavior. Partially adequate.

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?

Well-structured with bullet points and examples. Somewhat verbose due to docstring format (e.g., :param, :return). Front-loaded purpose. Could be tightened without losing clarity.

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?

Covers all parameters with examples and constraints (VDC jobs with network capture). Lacks info on return value structure (no output schema) and error handling. Fairly complete for a retrieval 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?

Schema coverage is 0%, but description details every parameter: job_id (required), filter_category (with enumerated list of 8 categories), custom_domains, resource_types, status_codes. Adds significant meaning beyond the schema's basic types and defaults.

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?

States verb+resource: 'Retrieves and filters HAR file data from a Sauce Labs test job'. Distinguishes from sibling 'filter_har_data' by noting it works for specific job context and provides predefined filter categories.

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?

Provides context: when to use (retrieve filtered network data from a job). Does not explicitly mention when not to use or alternatives (e.g., filter_har_data), though examples imply usage.

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