Skip to main content
Glama
Sign In
browser-mcp

browser-mcp

by hupeng9995
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_element_by_selector

Extract HTML and CSS styles from any webpage element using a CSS selector, with optional inclusion of child elements for comprehensive code analysis.

Instructions

通过CSS选择器获取元素的HTML和样式信息

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "selector": "<selector>"
    },
    "name": "get_element_by_selector"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorYesCSS选择器
includeChildrenNo是否包含子元素（默认：false）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided; the description does not disclose behavioral traits such as read-only nature, error behavior, or permissions required. It lacks transparency beyond the basic function.

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

Conciseness4/5

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

The description is a single, front-loaded sentence with no unnecessary words. It is concise and directly states the purpose.

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

Completeness2/5

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

Missing output schema; the description does not specify the return format (e.g., structure of HTML and style info) or error handling. For a two-parameter tool with no annotations, more detail would improve completeness.

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 description coverage is 100% for both parameters (selector, includeChildren). The tool description adds no extra meaning beyond the schema, meeting the baseline expectation.

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?

The description clearly states the verb 'get' and resource 'element' via CSS selector, and specifies that it retrieves both HTML and style info. It distinguishes from siblings like 'get_element_styles' (only styles) and 'get_page_source' (full page).

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 guidance on when to use this tool versus alternatives such as 'get_element_styles' or 'get_page_source'. No context on prerequisites or when not to use it.

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