You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
cookie-debugging skill tells agents to call navigate_page with reload: true, which the tool rejects #2906
skills/cookie-debugging/SKILL.md (workflow 1, step 4) tells agents to trigger a fresh request with "Use navigate_page with reload: true". navigate_page has no reload argument; reloads use type: "reload", and the server rejects unknown tool arguments. An agent that follows the skill verbatim gets a tool error instead of a reload. The skill text is identical in the 1.10.1 npm package and on main at b2f522c.
Actual behavior
On 1.10.1, step 3 returned isError: true with Unknown argument for tool "navigate_page": "reload". Expected arguments: "pageId", "type", "url", "ignoreCache", "handleBeforeUnload", "initScript", "timeout". Remove it and retry. On mainb2f522c it returned isError: true with Input validation error: Invalid arguments for tool navigate_page: Unrecognized key: "reload". The step 4 control returned Successfully reloaded the page. in both builds.
Reproduction
Executed on macOS against the published chrome-devtools-mcp@1.10.1 package and a local build of mainb2f522c, with usage statistics and update checks disabled.
npm i --prefix /tmp/x chrome-devtools-mcp@1.10.1 @modelcontextprotocol/sdk.
Start chrome-devtools-mcp --headless --isolated --no-usage-statistics --no-performance-crux under an MCP stdio client (I used @modelcontextprotocol/sdkClient + StdioClientTransport) and call list_pages.
Call navigate_page with arguments {"pageId": 1, "reload": true}, as the skill describes.
Control: call navigate_page with {"pageId": 1, "type": "reload"}.
Expectation
The skill's instruction should perform a reload. navigate_page reloads through type: "reload" (docs/tool-reference.md, navigate_page; schema in src/tools/pages.ts, type: zod.enum(['url', 'back', 'forward', 'reload'])), and since 1.0.0 the server reports unknown tool arguments (CHANGELOG 1.0.0, "report unknown tool arguments", #2064).
154.0.8037.93 (stable, launched by the server, headless, isolated)
Node version
v24.21.0
Operating system
macOS
Evidence
Expected source: docs/tool-reference.md (navigate_page) and src/tools/pages.ts (navigatePage schema) at tag chrome-devtools-mcp-v1.10.1 and mainb2f522c; CHANGELOG 1.0.0 entry for fix: report unknown tool arguments #2064.
Failure source: skills/cookie-debugging/SKILL.md:52 (identical in 1.10.1 and mainb2f522c) and the tool responses quoted under Actual behavior.
Evidence provenance: observed
Local verification: reproduced
Reproduction completeness: complete
Fix check
Failing now: the call the skill describes, navigate_page with reload: true, returns an unknown-argument error. Restored: the skill's instruction for triggering a reload, followed as written, produces Successfully reloaded the page. as the step 4 control does. Control: navigate_page keeps rejecting unknown arguments such as reload; restoration must not come from accepting undeclared arguments unless that contract is deliberately changed.
Description of the bug
skills/cookie-debugging/SKILL.md(workflow 1, step 4) tells agents to trigger a fresh request with "Usenavigate_pagewithreload: true".navigate_pagehas noreloadargument; reloads usetype: "reload", and the server rejects unknown tool arguments. An agent that follows the skill verbatim gets a tool error instead of a reload. The skill text is identical in the 1.10.1 npm package and onmainat b2f522c.Actual behavior
On 1.10.1, step 3 returned
isError: truewithUnknown argument for tool "navigate_page": "reload". Expected arguments: "pageId", "type", "url", "ignoreCache", "handleBeforeUnload", "initScript", "timeout". Remove it and retry.Onmainb2f522c it returnedisError: truewithInput validation error: Invalid arguments for tool navigate_page: Unrecognized key: "reload". The step 4 control returnedSuccessfully reloaded the page.in both builds.Reproduction
Executed on macOS against the published
chrome-devtools-mcp@1.10.1package and a local build ofmainb2f522c, with usage statistics and update checks disabled.npm i --prefix /tmp/x chrome-devtools-mcp@1.10.1 @modelcontextprotocol/sdk.chrome-devtools-mcp --headless --isolated --no-usage-statistics --no-performance-cruxunder an MCP stdio client (I used@modelcontextprotocol/sdkClient+StdioClientTransport) and calllist_pages.navigate_pagewith arguments{"pageId": 1, "reload": true}, as the skill describes.navigate_pagewith{"pageId": 1, "type": "reload"}.Expectation
The skill's instruction should perform a reload.
navigate_pagereloads throughtype: "reload"(docs/tool-reference.md,navigate_page; schema insrc/tools/pages.ts,type: zod.enum(['url', 'back', 'forward', 'reload'])), and since 1.0.0 the server reports unknown tool arguments (CHANGELOG 1.0.0, "report unknown tool arguments", #2064).MCP configuration
--headless --isolated --no-usage-statistics --no-performance-cruxChrome DevTools MCP version
1.10.1 (npm) and
mainb2f522c (local build)Chrome version
154.0.8037.93 (stable, launched by the server, headless, isolated)
Node version
v24.21.0
Operating system
macOS
Evidence
docs/tool-reference.md(navigate_page) andsrc/tools/pages.ts(navigatePageschema) at tagchrome-devtools-mcp-v1.10.1andmainb2f522c; CHANGELOG 1.0.0 entry for fix: report unknown tool arguments #2064.skills/cookie-debugging/SKILL.md:52(identical in 1.10.1 andmainb2f522c) and the tool responses quoted under Actual behavior.Fix check
Failing now: the call the skill describes,
navigate_pagewithreload: true, returns an unknown-argument error. Restored: the skill's instruction for triggering a reload, followed as written, producesSuccessfully reloaded the page.as the step 4 control does. Control:navigate_pagekeeps rejecting unknown arguments such asreload; restoration must not come from accepting undeclared arguments unless that contract is deliberately changed.