easy-ui-mcp

Overview Schema Source Related Servers Discussions Admin

ui_get_logs

ui_get_logs

Reads captured browser errors and failed requests from the current session so you can diagnose actions that appeared to do nothing; returns new logs by default or all logs with since start.

Instructions

Read the browser problems captured in this session so far: console errors, uncaught page errors, failed requests and HTTP 4xx/5xx responses (method + URL, never bodies or headers). Use it when an action seemed to do nothing. since: last (default) returns only what is new since the previous call; start returns everything. Pass level: warning to include console warnings. Repeats are grouped (×N); at most 50 lines.

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

Input Schema

Name	Required	Description
`level`	No	error (default), or warning to also include console warnings
`since`	No	last (default): new since the previous ui_get_logs; start: everything
`session_id`	No	Which open session to act on, as returned by ui_start_session. Optional with one open session; required when several are open.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A4.3/5.0

Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses the delta semantics ('since: last' returns only what is new since the previous call, i.e. the log is cumulative across calls), the output cap ('at most 50 lines'), deduplication behavior ('repeats are grouped ×N'), and a privacy boundary ('never bodies or headers'). These are the behavioral traits an agent needs to interpret results correctly and avoid misreading a short response as an empty log.

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?

Front-loaded with what is returned, then the trigger condition, then parameter behavior, then output shape. Every clause adds information (scope, trigger, delta, level, grouping, cap) with no filler or repetition.

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?

No output schema exists, so the description must describe return values itself, and it does: entry types, method+URL granularity, excluded payloads, grouping notation, and the 50-line ceiling. Combined with a fully documented 3-parameter schema, nothing material is missing for correct invocation or interpretation.

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 both enums are already documented in structured form. The description restates the same meanings for 'since' and 'level' without adding syntax, defaults beyond what the schema says, or interaction rules between them; 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 precise verb ('Read') and an enumerated resource (console errors, uncaught page errors, failed requests, HTTP 4xx/5xx with method + URL), so an agent knows exactly what data comes back. It never explicitly contrasts itself with adjacent readers like ui_get_page_state or ui_get_text, so the sibling boundary is left to inference.

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?

'Use it when an action seemed to do nothing' is a concrete trigger condition, which is more than most definitions offer. It does not say when not to use it or name an alternative tool for related diagnostics, leaving the routing decision partly implicit.

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