Clicks visible elements on a web page using a CSS selector, numeric ID, or text content.
Click a visible element.
Accepts a CSS selector, the numeric id from ``get_interaction_tree``
(e.g. ``"12"`` -> ``[data-zendriver-id="12"]``), or ``text`` to find
by visible text content.
| Name | Required | Description | Default |
|---|---|---|---|
| text | No | ||
| selector | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Does not disclose behavior on failure (e.g., element not found), waiting, or error handling. Only describes targeting methods.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with clear front-loading of purpose. No waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers purpose and targeting but misses error conditions and behavior upon success/failure. Output schema exists, so return values not needed, but more behavioral context would help.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Adds meaning by explaining that selector can be CSS or numeric id, and text is for visible text search. With 0% schema coverage, description compensates well but lacks info on conflicts if both provided.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it clicks a visible element, with specific targeting methods (CSS selector, data-zendriver-id, text). It distinguishes from siblings like human_click, click_shadow, and click_by_uid.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives like human_click or click_shadow. Does not specify prerequisites or context for use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/bituq/zendriver-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server