list_console_message TOO VERBOSE TOO MUCH TOKENS

[santoldev]

Describe the bug
The list_console_message tool is very verbose.
example: when copying directly from browser console its only 8k tokens.
when using list_console_messages tool its 40k tokens.
truncate or remove not important parts like timestamp t=1758906781192:597:24 too many of t=XXXX:line:line too many Log>
Right now this mcp is just another Playwright/puppeeter, unusable, the list_console_messages are too verbose , we cant actually use this for continues debuging, and there are no FILTER OPTION <--- very important
its also good to return only pure text without the objects or arrays.
Take note when i test this its all Pure text logs, no object/arrays console logging.

To Reproduce
do a real debugging with console logs , use list_console_messages, compare normal copy directly from browser console and compare with list_console_messages output. compare token length difference

Expected behavior
same or similar token count from Direct Copy vs list_console_messages.

Chrome version: LTS
Coding agent version: LTS
Model version: LTS

[santoldev]

i found the bug, the list_console_messages , repeats the same line 4x!
8k pure text x 4 = 32k + json formats and extra formattings. = 40k

[lifeinchords]

I'm new to all this.. not sure if I'm following or repeating but just in case..

Aside from the duplicate write error, filtering on Chrome side is really key, before returning any data.. the average volume of tokens in Chrome Console is just too much to digest and analyze.

Is there a way of passing filtering/regexes via the MCP tool, to selectively narrow, in the same way Chrome has these?
https://developer.chrome.com/docs/devtools/console/reference

key idea being Chrome does it on its side vs the MCP tool needing to parse/digest on the receiving side..