Skip to main content
Glama

Get extension logs

get_logs
Read-only

Retrieve and filter Chrome extension console output, including logs from before the current session. Use cursors, time ranges, levels, or search terms to find specific entries.

Instructions

Get console output from Chrome extensions that use the stdout-mcp library, including output from before this session started. Without after, returns the most recent matching entries. With after, returns the entries following that cursor, oldest first. With around, returns the entries before and after that one.

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": "get_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoCursor from a previous result. Only entries after it are returned.
limitNoMaximum number of entries to return. Defaults to 100, or 21 with `around`.
sinceNoOnly include entries from this long ago or later, like "30s", "10m" or "2h", or from a local time like "2026-10-20 16:35".
aroundNoEntry number to center the results on, such as one found with `search`. Filters apply to the entries around it.
levelsNoConsole methods to include, like ["error", "warn"]. Defaults to all.
searchNoCase-insensitive regular expression to match against the message text.
browserNoOnly include logs from this browser, by the name or ID that list_sources shows.
filenameNoOnly include logs from pages or scripts whose filename contains this, like "popup".
extensionNoOnly include logs from this extension, by ID or exact name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With only readOnlyHint declared, the description adds real behavioral context: it discloses that pre-session output is included and specifies result ordering per mode (most recent first without `after`, oldest first with `after`, both sides with `around`). It stops short of describing entry structure, truncation, or what happens when no entries match.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the purpose and then the three retrieval modes in a consistent 'Without/With/With' pattern. No filler, no restatement of the title.

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?

For a nine-parameter read tool with no output schema, the definition covers purpose, default behavior, and the cursor modes that an agent most needs to call it correctly. The remaining gap is the shape of returned entries and how cursor values are obtained, which the description only gestures at via the `around` example.

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 coverage is 100%, so each of the nine parameters is already documented inline, including the default limit shift to 21 with `around`. The description reinforces the cursor semantics and ordering but adds little beyond what the schema states, so the baseline 3 applies.

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?

The description gives a specific verb and resource ('Get console output from Chrome extensions') and narrows scope to those using the stdout-mcp library, plus a notable inclusion ('output from before this session started'). It does not explicitly differentiate itself from siblings like wait_for_log or list_sources, which keeps it short of a 5.

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?

It clearly explains the three calling modes keyed on `after` and `around`, which tells an agent how to shape a request. However, it offers no guidance on when this tool is preferable to wait_for_log (polling/live tailing) or list_sources, so the alternative-selection question is left to inference.

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