Cloud Tool Results API

Name: Cloud Tool Results API API
Brand: Cloud Tool Results API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsTesting Qaoauth229 EndpointsREST

For Agents

Read detailed Firebase Test Lab results — histories, executions, steps, screenshots, videos, performance metrics, and per-test-case outcomes.

Quickstart

Get started with Cloud Tool Results API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get firebase test lab results"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Cloud Tool Results API API.

Query histories grouped by app package and version

List executions and individual step results within an execution

Retrieve per-step performance metrics, screenshots, and video clusters

Inspect individual test-case outcomes (passed, failed, flaky, skipped)

GET STARTED

Start building with Cloud Tool Results API API

Explore with Jentic

View OpenAPI Document

Cloud Tool Results stores and serves the detailed output of Firebase Test Lab runs and other Google developer-tooling executions. Results are organised hierarchically as histories (one per app), executions (one per matrix run), steps (one per device-execution combination), and per-step artefacts including logcat, screenshots, video, performance metrics, and test-case results. The API is the backbone behind the Firebase Test Lab UI in the Google Cloud Console and is what teams call when they need programmatic access to deep test diagnostics.

Use Cases

Patterns agents use Cloud Tool Results API API for, with concrete tasks.

★ Failure Triage Dashboard

QA leads build a triage dashboard that pulls failing steps across recent executions, ranks them by frequency, and groups them by device model and OS version. The dashboard polls /toolresults/v1beta3/projects/{projectId}/histories/{historyId}/executions for new runs and drills into steps and test-cases to extract failure reasons. Engineers see device-specific patterns (e.g. 'Galaxy S22 + Android 14 fails 80% of the time') without opening the Firebase Console.

List executions for a history, then for each execution iterate steps and call the test-cases endpoint to count failed cases keyed by device model.

Screenshot Diff for Visual Regressions

Mobile teams capture screenshots from each Test Lab run via Robo crawl or instrumentation, retrieve them through Tool Results, and feed them into a visual-diff pipeline. The screenshot clusters endpoint groups perceptually similar images, making it straightforward to identify new UI states introduced by a release and flag visual regressions.

GET /toolresults/v1beta3/projects/{projectId}/histories/{historyId}/executions/{executionId}/clusters and download each screenshot URL for diffing.

Performance Trend Tracking

Performance teams pull per-step performance metrics from each Test Lab execution and chart trends over time. Metrics like CPU usage, memory, and frame timing are exposed under the perfMetricsSummary and perfSampleSeries endpoints. Sudden regressions in startup time or frame drop rate are flagged before the build promotes to production.

GET /toolresults/v1beta3/projects/{projectId}/histories/{historyId}/executions/{executionId}/steps/{stepId}/perfMetricsSummary and store the cpu and memory series for trend analysis.

Agent-Generated Test Failure Report via Jentic

A release agent monitors Test Lab and produces a written summary of any new run. Through Jentic the agent calls Tool Results to list failed steps, fetch logcat, and retrieve representative screenshots, then composes a release note attached to the build. Jentic isolates the OAuth credential across the multi-step retrieval.

Through Jentic, search 'list firebase test lab steps', load the steps endpoint, iterate failing steps and pull thumbnails plus logcat URIs to compose a Markdown summary.

Key Endpoints

29 endpoints — cloud tool results stores and serves the detailed output of firebase test lab runs and other google developer-tooling executions.

METHOD

PATH

DESCRIPTION

GET

/toolresults/v1beta3/projects/{projectId}/histories

List histories for a project

GET

/toolresults/v1beta3/projects/{projectId}/histories/{historyId}/executions

List executions in a history

GET

/toolresults/v1beta3/projects/{projectId}/histories/{historyId}/executions/{executionId}

Retrieve a single execution

GET

/toolresults/v1beta3/projects/{projectId}/histories/{historyId}/executions/{executionId}/clusters

List screenshot clusters from an execution

GET

/toolresults/v1beta3/projects/{projectId}/histories/{historyId}/executions/{executionId}/clusters/{clusterId}

Retrieve a single screenshot cluster

GET

/toolresults/v1beta3/projects/{projectId}/histories

List histories for a project

GET

/toolresults/v1beta3/projects/{projectId}/histories/{historyId}/executions

List executions in a history

GET

/toolresults/v1beta3/projects/{projectId}/histories/{historyId}/executions/{executionId}

Retrieve a single execution

GET

/toolresults/v1beta3/projects/{projectId}/histories/{historyId}/executions/{executionId}/clusters

List screenshot clusters from an execution

GET

/toolresults/v1beta3/projects/{projectId}/histories/{historyId}/executions/{executionId}/clusters/{clusterId}

Retrieve a single screenshot cluster

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Service-account credentials are stored encrypted in the Jentic vault. Agents fetch test results through Jentic without ever seeing the raw OAuth tokens or the GCS signing keys for artefact download.

Intent-based discovery

Agents search 'get firebase test lab results' or 'list test execution steps' and Jentic returns the matching v1beta3 endpoint with its full path-template schema.

Time to first call

Direct Tool Results integration: 2-4 days to walk the histories→executions→steps→test-cases hierarchy and wire artefact download. Through Jentic: under 1 hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Cloud Testing API

Submits the test matrices whose results Tool Results then exposes

Always use together — Cloud Testing submits the run, Tool Results reads back the detailed step-by-step outcomes.

Complementary

Firebase Management API

Manage the Firebase project that owns the Test Lab results history

Use Firebase Management to provision the project; Tool Results reads under that project's history namespace.

Complementary

Google Cloud Storage API

Underlying object store holding test artefacts referenced by Tool Results

Use Cloud Storage to download the actual logcat, video, and screenshot bytes after Tool Results returns the GCS URI.

FAQs

Specific to using Cloud Tool Results API API through Jentic.

What authentication does the Cloud Tool Results API use?

OAuth 2.0 with the cloud-platform scope is required for read access. CI integrations typically use service-account credentials that have the testlab.viewer role on the project. Through Jentic, the service-account JSON is held in the encrypted vault and short-lived tokens are minted for each call.

Can I retrieve screenshots from a Test Lab run with the Cloud Tool Results API?

Yes. Screenshots from Robo crawl runs are exposed as clusters under /toolresults/v1beta3/projects/{projectId}/histories/{historyId}/executions/{executionId}/clusters. Each cluster groups perceptually similar screenshots and exposes thumbnails plus full-resolution images stored in Cloud Storage.

What are the rate limits for the Cloud Tool Results API?

Tool Results enforces standard Google Cloud per-project read quotas, generally allowing several hundred reads per minute per project. Polling executions for completion should use the Cloud Testing API state field rather than tight loops over Tool Results endpoints. Back off on 429 responses with exponential delay.

How do I find failing test cases through Jentic?

Search Jentic for 'list firebase test lab steps', load the steps endpoint, then for each step call the test-cases sub-resource and filter where outcome.summary equals FAILURE. Jentic returns the parsed JSON so the agent can summarise without parsing the URL hierarchy by hand. Get started at https://app.jentic.com/sign-up.

Does the Cloud Tool Results API expose logcat and video?

Yes. Each step has a list of test artefacts (testIssues, outputs) that include logcat, video files, and crash logs as Cloud Storage URIs. The artefacts are served from a project-scoped GCS bucket and require the same project credentials to download.

Is the Cloud Tool Results API free?

Yes, the API itself is free. Storage of the test artefacts (videos, logs, screenshots) is billed at Cloud Storage rates against the Test Lab results bucket; older results can be deleted via lifecycle rules to manage cost.