Skip to main content
Glama
Sign In
Puppeteer Debugger MCP Server

Puppeteer Debugger MCP Server

by ALIEX7664
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

check_element

Inspect a web element's attributes, CSS styles, and visibility by providing a CSS selector. Optionally specify a page URL to check elements on that page.

Instructions

检查元素状态（属性、样式、可见性等）

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": "check_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorYesCSS 选择器
urlNo页面 URL（可选）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the tool modifies state, requires specific permissions, or handles missing elements. It only states it 'checks' state, which implies read-only but is not explicit.

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 concise sentence that conveys the core functionality without waste. It could benefit from slightly more detail but remains efficient for a simple tool.

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?

Given the tool's simplicity and lack of output schema, the description covers the main use (checking attributes, styles, visibility) but omits return format, error behavior, and any performance implications, leaving some gaps for an AI agent.

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. The description adds no additional meaning beyond the schema's own descriptions (CSS selector, optional page URL). The baseline score of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the tool's purpose: checking element state including attributes, styles, visibility. It effectively distinguishes from sibling tools which focus on memory, cache, console errors, performance, navigation, screenshots, and allocations.

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?

The description provides no guidance on when to use this tool vs alternatives, nor does it mention conditions or prerequisites. It does not reference any sibling tools or suggest when to choose this tool.

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