Skip to main content
Glama

browserless_performance_run

Read-only

Run a prepared Lighthouse performance audit in widget-only mode; repeated calls reuse the same audit via auditRef.

Instructions

Widget-only execution of a prepared Lighthouse audit. Repeated requests reuse the same audit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "auditRef": "<auditRef>"
    },
    "name": "browserless_performance_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
auditRefYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.47.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's job is to add nuance. It does: 'Repeated requests reuse the same audit' discloses caching/deduplication behavior that an agent could not infer from annotations, and 'widget-only' hints at an environment restriction. It stops short of describing what happens when the audit is not prepared or how long execution takes.

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?

Two short sentences, front-loaded with the core action and followed by the runtime behavior. Nothing is wasted, though 'Widget-only' is undefined jargon that costs the reader a beat.

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?

For a one-parameter execution tool whose safety profile is covered by annotations and which has no output schema, the description is close to sufficient. However, the undefined 'widget-only' constraint and the absence of any statement about the return value or error behavior leave gaps for a tool that triggers an audit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter auditRef has 0% schema description coverage (only a UUID format is declared), so the description must carry the meaning. It partially does by tying it to a 'prepared Lighthouse audit,' implying the value comes from a prior preparation step, but it never states that explicitly or explains scoping, reuse, or failure semantics of the reference.

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?

States a specific verb and resource: 'execution of a prepared Lighthouse audit.' The qualifier 'prepared' distinguishes it from an audit-creation tool, but the opaque phrase 'Widget-only' and the failure to name the sibling that produces the auditRef leave a small ambiguity about exactly which step of the workflow this covers.

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?

Usage is only implied: 'prepared' signals a precondition that an audit must exist before calling this, but there is no explicit statement of when to call this versus browserless_performance or browserless_performance_result, and no guidance on what to do if the reference is invalid.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.