Skip to main content
Glama
Sign In
Puppeteer Real Browser MCP Server

Puppeteer Real Browser MCP Server

by withLinda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

find_selector

Find the CSS selector for an element containing specific text. Optionally match exact text or restrict to a given element type.

Instructions

Find CSS selector for element containing specific text

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": {
      "text": "<text>"
    },
    "name": "find_selector"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText content to search for in elements
exactNoWhether to match exact text (true) or partial text (false)
elementTypeNoHTML element type to search within (e.g., "button", "a", "div"). Default is "*" for any element*

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.0

TDQS

B3.4/5.0
Behavior2/5

Does 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 not disclose the return format, what happens on no match or multiple matches, or whether it performs a read-only DOM search. The behavior is only vaguely implied.

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?

The description is a single, compact sentence that efficiently conveys the core function without any redundant words. It earns its place by adding specific detail beyond the tool name.

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?

With no output schema and no annotations, the description should clarify return values and edge-case behavior. It does not state whether it returns a string, an array, or throws on missing text, leaving significant gaps for autonomous use.

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?

The input schema covers 100% of the parameters with clear descriptions. The tool description adds no extra meaning beyond the schema, so it meets the baseline but does not enhance parameter understanding.

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 uses a specific verb and resource ('Find CSS selector for element containing specific text'), making it clear what the tool does. It also distinguishes itself from sibling tools like click or navigate by focusing on selector discovery.

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

Usage Guidelines3/5

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

The usage is implied by the purpose: use this tool when you need a CSS selector for an element by its text. However, there is no explicit guidance on when not to use it or how it compares to alternatives.

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