Skip to main content
Glama
Sign In
DrissionPage-MCP

DrissionPage-MCP

by hooplus1ce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

选择下拉项

element_select

Select an option in a dropdown using visible text, value attribute, or index. Specify the element ID and matching criteria for precise browser automation.

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": {
      "element_id": "<element_id>",
      "by": "<by>",
      "value": "<value>"
    },
    "name": "element_select"
  }
}

Input Schema

NameRequiredDescriptionDefault
byYes选择方式：text=按可见文本, value=按 value 属性, index=按序号（从 1 开始）
valueYes匹配的文本 / value / 序号
element_idYesfind_element 返回的 <select> 元素 id

Output Schema

NameRequiredDescriptionDefault
okYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

The description does not disclose behavioral details beyond the annotation readOnlyHint=false, such as whether the action triggers change events, requires element visibility, or how it handles invalid options. It adds minimal transparency beyond the annotation itself.

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, concise sentence that fully conveys the tool's purpose without unnecessary words or redundancy. It is well-structured and directly to the point.

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?

Given that the schema fully describes all parameters and an output schema is present, the description is sufficiently complete for a simple select operation. It does not explain error cases, but such details are not essential for this level of simplicity.

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 schema already covers all three parameters with descriptions (by, value, element_id). The tool description adds no additional meaning beyond what the parameter descriptions already provide, so it meets the baseline for high schema coverage.

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 action: 'Select an option in the dropdown box (<select>) element.' It is a specific verb+resource combination that distinguishes it from sibling tools like antd_select and vtable_click_cell.

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 explicit guidance is given on when to use this tool over alternatives. It does not mention that it targets native HTML <select> elements or contrast it with antd_select for Ant Design components, leaving the agent to infer the appropriate context.

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