Skip to main content
Glama
Yan-Vi

easy-spec-mcp

by Yan-Vi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

live_pick_element

Starts an interactive element picker on the target browser tab, waits for a user click, and returns the generated locator expression for use in automation scripts.

Instructions

Starts the element picker on the side panel's target tab (the pinned tab, or the active tab if none is pinned) and waits (up to 2 minutes) for the user to click something, returning the resulting locator expression -- the same picker the step editor's "Pick element" button uses, generated by the real Playwright engine (Locator.generateLocatorString()), ready to use as-is with set_locator/set_scope or a step's own selector. Requires the side panel open and connected. Pass pageObject+scope to restrict picking to that page object's named scope (see set_scope) -- only elements inside the scope's own root element are hoverable/clickable. The scope must be non-parametric -- a scope reused per row/instance has no single element to confine picking to here.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNo
projectNoPath to the project root (same folder the side panel connects to). Defaults to the EASYSPEC_PROJECT environment variable if omitted.
sessionNoWhich connected side panel to target, by its connection id (see live_status) -- only needed when more than one side panel is connected to the same project.
pageObjectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.4

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden. It discloses the wait timeout, the user interaction requirement, and the non-parametric scope restriction. It does not mention potential side effects like tab focus changes, but the core behavior is transparent.

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

Conciseness3/5

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

The description is a single verbose run-on sentence with repeated references to the side panel and page object. It contains valuable information but would benefit from clearer structure and more concise phrasing.

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

Completeness4/5

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

The description explains the return value (locator expression), prerequisites, timeout, and parameter usage. It lacks explicit error conditions or a formal return schema, but the information provided is sufficient for an agent to invoke the tool correctly.

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

Parameters4/5

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

The schema provides descriptions for project and session, and the tool description supplements scope and pageObject with meaningful details (e.g., scope must be non-parametric, pageObject restricts picking). This effectively covers all four parameters, though the schema itself only covers 50%.

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 starts an interactive element picker on the side panel's target tab and returns a locator expression. It is specific about the action and resource, and it is distinct from sibling live_* tools.

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

Usage Guidelines4/5

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

The description explains prerequisites (side panel open and connected), how to restrict picking via pageObject and scope, and how the result can be used with set_locator/set_scope. It lacks an explicit comparison to alternative tools, but the interactive nature is clear.

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