Moves the scraping browser forward to the next page in its history, letting AI assistants continue navigating previously visited pages during data collection.
Go forward to the next page
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v3.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, non-destructive, open-world behavior, so the safety profile is covered. The description adds nothing: it doesn't disclose that this acts on session history, nor what happens when there is no forward entry (likely a no-op or error).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One short sentence, front-loaded with the verb, zero filler. Its brevity is efficient, though it leans on completeness rather than conciseness for its gaps.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
A trivial zero-param tool whose annotations already carry the safety profile, so the burden is light. Still missing is the key context: that this is history navigation tied to prior go_back/navigate calls and how it behaves when no forward page exists.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Zero parameters, so there is nothing to document; baseline 4 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('go forward') and object ('next page'), which reads as browser history navigation and pairs naturally with the sibling scraping_browser_go_back. It does not explicitly say 'browser history', so 'next page' could be mistaken for pagination, but the sibling set disambiguates.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No statement of when to use this versus scraping_browser_navigate or scraping_browser_go_back, and no mention that it requires an existing browser session with forward history. The agent must infer all of that.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.