browser_extract_linksExtract all unique links from the current browser tab with their resolved final URLs. Provides a deduplicated list of links for analysis or subsequent actions.
List all links (deduplicated) with their resolved hrefs.
| Name | Required | Description | Default |
|---|---|---|---|
| tab | No | ||
| limit | No | ||
| session | No | default |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It does disclose meaningful behavior: links are deduplicated and hrefs are resolved. It does not explain edge cases like whether only anchor tags are included, but the core non-obvious behaviors are stated.
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?
The description is a single, front-loaded sentence with no filler. Every word adds meaning, and the key qualifiers are placed immediately after the action.
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?
The description is too sparse for a tool with three undocumented parameters and no annotations. An agent cannot tell what tab, session, or limit mean, and the 'all links' wording obscures the effect of the default limit.
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?
Schema description coverage is 0%, and the description mentions none of the three parameters: tab, limit, or session. The phrase 'List all links' even conflicts with the default limit of 100, leaving the agent unable to infer parameter behavior.
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?
The description uses a specific verb and resource: 'List all links' with two clarifying qualifiers, 'deduplicated' and 'resolved hrefs.' This clearly distinguishes it from sibling tools like browser_extract_text, browser_extract_html, and browser_extract_tables.
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?
The description gives no guidance on when to use this tool instead of browser_extract_html, browser_find, or browser_snapshot. No alternatives, exclusions, or contextual trigger conditions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.