Skip to main content
Glama
Mehmoodqureshi

MCP Browser Extension

by Mehmoodqureshi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

extract_links

Collect hyperlinks from a Chrome page or DOM subtree, optionally deduplicating repeated hrefs to cut nav/footer noise and limiting results.

Instructions

Extract anchors from the page or a subtree. dedupe=true collapses links sharing an href (nav/footer noise); limit caps the count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
tabIdNoTab id (default: agent's tab)
dedupeNo
frameIdNoFrame id from frames_list
selectorNo
allFramesNoAct on the first match in ANY frame (the element may be in an iframe)
sameOriginOnlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.24
    • changedInput schema / properties / tabId / description
      Previous value: -"Tab id (default: active tab)"New value: +"Tab id (default: agent's tab)"
  2. Changed3 schema fields changedv0.9.5
    • changedInput schema / properties / allFrames / description
      Previous value: -"Search every frame of the tab and act on the first that matches - use when a selector should match but does not (the element is in an iframe)"New value: +"Act on the first match in ANY frame (the element may be in an iframe)"
    • changedInput schema / properties / frameId / description
      Previous value: -"Act inside this frame (ids come from frames_list)"New value: +"Frame id from frames_list"
    • changedInput schema / properties / tabId / description
      Previous value: -"Target tab id (defaults to the active tab)"New value: +"Tab id (default: active tab)"
  3. Changed2 schema fields changedv0.7.0
    • addedInput schema / properties / allFrames
      Added value: +{
+  "description": "Search every frame of the tab and act on the first that matches - use when a selector should match but does not (the element is in an iframe)",
+  "type": "boolean"
+}
    • addedInput schema / properties / frameId
      Added value: +{
+  "description": "Act inside this frame (ids come from frames_list)",
+  "type": "number"
+}
  4. Changed2 schema fields changedv0.6.6
    • addedInput schema / properties / dedupe
      Added value: +{
+  "type": "boolean"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "type": "number"
+}
  5. First observedv0.6.2

TDQS

B3.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the full burden. It usefully explains that dedupe collapses links sharing an href (with the reason: nav/footer noise) and that limit caps the count, but says nothing about the return shape, failure on missing matches, or which frame/tab defaults apply.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the core action, then the two non-obvious parameter behaviors. Nothing is wasted and no filler is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter extraction tool with no annotations and no output schema, the description leaves real gaps: the return format (href/text objects vs strings), the meaning of selector/sameOriginOnly, and default tab behavior. It covers the delimiter behavior well but not enough to be complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 43% (tabId, frameId, allFrames documented), so the description should compensate. It meaningfully explains dedupe and limit, but leaves selector and sameOriginOnly completely undocumented in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Extract anchors from the page or a subtree"), which is clearly distinct from siblings like get_text, get_html, and snapshot. It does not explicitly name or contrast with those siblings, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance and no alternatives are mentioned. The agent must infer that this is the link-specific extraction tool versus get_html or read_as_markdown, which the description never addresses.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools