Google Cloud Tool Results API

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

✓ Official Vendor SpecDeveloper ToolsTesting Qaoauth229 Endpoints

Install Jentic One Beta

Connect the Cloud Tool Results API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloud Tool Results API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Cloud Tool Results 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

GET STARTED

Start building with Cloud Tool Results API

Explore with Jentic

View OpenAPI Document

For Agents

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

Use for: I need to fetch the test results for a Firebase Test Lab run, List all executions in a test history, Get the per-step results for an execution, Find all failing test cases in a recent run

Not supported: Does not submit tests, control devices, or build artefacts - use for reading Firebase Test Lab execution results, steps, and artefacts only.

Use Cases

Patterns agents use Cloud Tool Results 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 Jentic?

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

Credential isolation

Your Cloud Tool Results service-account credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get firebase test lab results' or 'list test execution steps', and Jentic returns the matching Tool Results v1beta3 operation with its path-template input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Cloud Tool Results 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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Cloud Tool Results API?

Yes. Because Jentic One is self-hosted, you write the rules that decide which operations and credentials your agent may use. The Cloud Tool Results API puts the project and history in the URL path, so you can pin the agent to a single project and let it read only executions, steps, and screenshot clusters there and nothing else. Every operation here is read-only, so the agent can fetch test results but can never mutate or delete the underlying test data.