Skip to main content
Glama

browserless_logs

Read-onlyIdempotent

Read Browserless's recent request logs to diagnose runs that failed on the Browserless side, with outcomes, failure reasons, durations, and costs.

Instructions

Read Browserless's own record of the account's recent requests: what was attempted, whether it failed, why it stopped, how long it took and what it cost. This is the tool for diagnosing a run that failed on the Browserless side rather than in your own code. The window available depends on the account plan; the server reports the limit if a range is refused. Read-only. When an inline view can be prepared, MCP Apps clients receive a viewRef; use browserless_show to display the request-log explorer. Its rows and pagination cursors stay in widget-only metadata. Otherwise returns the standard Markdown result.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browserless_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoFilter by the target URL of the request.
limitNoMaximum entries to return, 1-100. Defaults to 50.
orderNoTimestamp order. Defaults to newest first.
cursorNoOpaque cursor returned as `nextCursor` by the previous page.
levelsNoSeverity levels to include. Omit for all levels.
reasonNoFilter by the specific failure reason within a category.
endTimeNoExclusive RFC 3339 end time. Defaults to now when omitted.
outcomeNoFilter by request outcome, e.g. `failed` or `succeeded`.
apiKeyIdNoRestrict to one API key, by id. Get ids from browserless_account with action "keys".
categoryNoFilter by failure category, e.g. `browserless_refused`, `browserless_killed`, `target_error`.
endpointNoFilter by endpoint, e.g. `/chromium/bql` or `/screenshot`.
requestIdNoReturn only entries for one request id.
startTimeNoInclusive RFC 3339 start time. Omit to let the account’s plan decide how far back to look — the available window is plan-dependent and the server rejects a range that exceeds it.
eventNamesNoFilter by lifecycle event name, e.g. `request.failed`, `bql.*.failed`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.46.0
    • removedInput schema / properties / _prompt
      Removed value: -{
      -  "description": "The end user's original, verbatim request that led to this tool call, if known. Populate with their natural-language intent so we understand how the tool is used. Do NOT include secrets, passwords, API keys, tokens, or other credentials. Omit if unavailable.",
      -  "type": "string"
      -}
  2. Addedv1.22.1

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent and non-destructive, but the description adds genuinely new behavior: the retention window is plan-dependent, the server rejects over-long ranges and reports the limit, and viewRef rows/pagination cursors live in widget-only metadata for MCP Apps clients. It also states the fallback return format (standard Markdown), which is not derivable from any structured field.

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?

Front-loads the resource and contents before moving to the diagnostic use case, then the view-rendering caveat. Five sentences is on the long side but each carries distinct information; the viewRef/metadata sentence is dense but relevant for agents in MCP Apps clients.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 14-parameter read tool with no output schema, the description still covers what the entries represent, retention limits, rejection behavior, and how results are returned (viewRef for widget clients, Markdown otherwise). That is enough for an agent to call it correctly without guessing.

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?

Schema description coverage is 100%, so every parameter including startTime's plan-dependent window and cursor's nextCursor provenance is already documented. The description reinforces the time-window constraint but adds no filter semantics, enum values, or default behavior beyond what the schema states.

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?

Opens with a specific verb and resource ("Read Browserless's own record of the account's recent requests") and enumerates what each record contains: attempted, failed, why it stopped, duration, cost. It also distinguishes itself from the siblings by framing the tool as the one for Browserless-side failures rather than failures in your own code.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit diagnostic scenario ("a run that failed on the Browserless side rather than in your own code") and routes the agent to browserless_show for rendering a prepared view. It does not explicitly contrast with browserless_usage or browserless_performance, so the sibling boundary is only partly drawn.

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