tool for listing in-page tools

Author: wolfib

README.md

@@ -475,6 +475,8 @@ If you run into any issues, checkout our [troubleshooting guide](./docs/troubles
   - [`list_console_messages`](docs/tool-reference.md#list_console_messages)
   - [`take_screenshot`](docs/tool-reference.md#take_screenshot)
   - [`take_snapshot`](docs/tool-reference.md#take_snapshot)
+- **In-page tools** (1 tools)
+  - [`list_in_page_tools`](docs/tool-reference.md#list_in_page_tools)
 
 <!-- END AUTO GENERATED TOOLS -->
 
@@ -566,6 +568,11 @@ The Chrome DevTools MCP server supports the following configuration option:
   - **Type:** boolean
   - **Default:** `true`
 
+- **`--categoryInPageTools`/ `--category-in-page-tools`**
+  Set to true to enable tools exposed by the inspected page itself
+  - **Type:** boolean
+  - **Default:** `false`
+
 - **`--performanceCrux`/ `--performance-crux`**
   Set to false to disable sending URLs from performance traces to CrUX API to get field performance data.
   - **Type:** boolean

docs/tool-reference.md

@@ -37,6 +37,8 @@
   - [`list_console_messages`](#list_console_messages)
   - [`take_screenshot`](#take_screenshot)
   - [`take_snapshot`](#take_snapshot)
+- **[In-page tools](#in-page-tools)** (1 tools)
+  - [`list_in_page_tools`](#list_in_page_tools)
 
 ## Input automation
 
@@ -397,3 +399,15 @@ in the DevTools Elements panel (if any).
 - **verbose** (boolean) _(optional)_: Whether to include all possible information available in the full a11y tree. Default is false.
 
 ---
+
+## In-page tools
+
+### `list_in_page_tools`
+
+**Description:** Lists all in-page-tools the page exposes for providing runtime information.
+In-page-tools are exposed on the page via the 'window.\_\_dtmcp.executeTool(toolName, params)'
+function where they can be called by '[`evaluate_script`](#evaluate_script)'.
+
+**Parameters:** None
+
+---