Files
Nikolay Vitkov d5d2f08a31 docs: fix some reported issues (#3099)
Fixes #3032, 
Fixes #3012
Fixes #3007
Fixes #2992
Fixes #2965
Fixes #2911

Issue | Summary | Evaluation | Fix Applied
-- | -- | -- | --
#3032 | evaluate_script args description does not say that strings are
snapshot element UIDs | Valid & Confirmed. The
outer zod.array(...).describe(...) on args in evaluateScript only
said "An optional list of arguments to pass to the function.", omitting
that each string is an element uid from the page content snapshot (which
caused both docs/tool-reference.md and src/config/cli-options.ts to omit
this). | Updated the args schema description in src/tools/script.ts and
regenerated docs/tool-reference.md and src/config/cli-options.ts.
#3012 | debug-optimize-lcp skill's resourceTypes: ["Image",
"Font"] filter is rejected by list_network_requests | Valid &
Confirmed. list_network_requests validates resourceTypes against
lowercase values ("image", "font", etc.), so capitalized values fail
input validation. | Updated Step 4
in skills/debug-optimize-lcp/SKILL.md to use resourceTypes: ["image",
"font"].
#3007 | Four chrome-devtools-cli skill examples fail as written | Valid
& Confirmed. In skills/chrome-devtools-cli/SKILL.md: (1) navigate_page 1
--handleBeforeUnload "accept" lacked --type or --url;
(2) performance_analyze_insight 1 "1" "LCPBreakdown" used "1" instead of
a valid insightSetId like "NAVIGATION_0"; (3) get_network_request 1
--responseFilePath "res.md" lacked --reqid; (4) list_network_requests 1
--resourceTypes Fetch used capitalized Fetch instead of fetch. | Updated
all four examples in skills/chrome-devtools-cli/SKILL.md.
#2992 | --allowUnrestrictedPaths help says only file-writing tools are
restricted, but file-reading upload_file is restricted too | Valid &
Confirmed. validateToolFiles in ToolHandler restricts local file-reading
parameters (such
as upload_file's filePaths and evaluate_script's sourcePath) as well as
file-writing tools when no MCP roots are configured. | Updated the
option description in src/config/mcp-options.ts, the startup warning
in src/index.ts, the comment in McpContextOptions, and
regenerated docs/configuration.md.
#2965 | A later emulate call silently clears the
earlier viewport, userAgent and colorScheme, which the tool description
does not say | Valid & Confirmed. McpPage.emulate() resets all omitted
emulation settings on every call (except extraHttpHeaders),
but emulate did not mention this in the tool description or
on userAgent, colorScheme, media features, or viewport, and the CLI
skill listed separate emulate calls without noting that each replaces
previous settings. | Updated the tool and parameter descriptions
in src/tools/emulation.ts, added a note and updated comments
in skills/chrome-devtools-cli/SKILL.md, and
regenerated docs/tool-reference.md and src/config/cli-options.ts.
#2911 | troubleshooting skill searches files that do not hold MCP server
configuration | Valid & Confirmed. Step 1
of skills/troubleshooting/SKILL.md searched .claude/settings.json and .vscode/launch.json instead
of .vscode/mcp.json (VS Code workspace MCP config)
and ~/.claude.json (Claude Code user/local MCP config). | Updated Step 1
in skills/troubleshooting/SKILL.md to
search .mcp.json, .vscode/mcp.json, gemini-extension.json, .gemini/settings.json,
and ~/.claude.json.
2026-10-13 13:17:48 +00:00
..