feat: Add pagination list_network_requests #145
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…equests_pagination
Contributor
Author
OrKoN
reviewed
Sep 25, 2025
Collaborator
OrKoN
left a comment
OrKoN
left a comment
There was a problem hiding this comment.
Thanks for the PR. Looks good, one question about pageToken (see inline).
Collaborator
|
Thanks! |
OrKoN
approved these changes
Sep 25, 2025
OrKoN
pushed a commit
that referenced
this pull request
Sep 25, 2025
🤖 I have created a release *beep* *boop* --- ## [0.3.0](chrome-devtools-mcp-v0.2.7...chrome-devtools-mcp-v0.3.0) (2025-09-25) ### Features * Add pagination list_network_requests ([#145](#145)) ([4c909bb](4c909bb)) ### Bug Fixes * avoid reporting page close errors as errors ([#127](#127)) ([44cfc8f](44cfc8f)) * clarify the node version message ([#135](#135)) ([0cc907a](0cc907a)) * do not set channel if executablePath is provided ([#150](#150)) ([03b59f0](03b59f0)) * **performance:** ImageDelivery insight errors ([#144](#144)) ([d64ba0d](d64ba0d)) * roll latest DevTools to handle Insight errors ([#149](#149)) ([b2e1e39](b2e1e39)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
OrKoN
pushed a commit
that referenced
this pull request
Sep 26, 2025
### Summary This PR build upon #145 to also adds filtering by resource type to `list_network_requests` (Also see: #137 and #107). ### Motivation Agents often need specific request types (e.g., scripts, stylesheets, images). Filtering reduces noise and improves performance. ### Changes - **New parameter**: `resourceType` (array) to filter by resource types - **Supported types**: all resource types supported by Puppeteer - **Backward compatible**: when omitted, returns all requests Filtering runs before pagination, so pagination applies to the filtered results.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR enhances the
list_network_requeststool with pagination support to handle large numbers of network requests efficiently. See this issue.Motivation
In my experience, the
list_network_requeststool frequently hits LLM token limits on pages with many requests, making it unusable for modern web applications. I wanted to add pagination to allow agents to be more flexible and manage token limits on their own.Changes
Pagination Support
pageSizeparameter to limit requests per callpageTokenparameter for navigation between pagesImplementation Details
src/utils/pagination.ts- generic pagination functionsetIncludeNetworkRequests()Testing
Backward Compatibility