Skip to main content
Glama
Sign In
DrissionPage-MCP

DrissionPage-MCP

by hooplus1ce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

输入文本

element_input

Fill text into an input field using its element ID, with options to clear existing content or assign via JavaScript.

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

Input Schema

NameRequiredDescriptionDefault
textYes要输入的文本
by_jsNo是否改用 JS 赋值
clearNo输入前是否清空已有内容
element_idYesfind_element 返回的元素 id

Output Schema

NameRequiredDescriptionDefault
okYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

The description indicates a write operation (input text), and the readOnlyHint=false annotation is consistent. It does not disclose potential side effects like triggering events or clearing existing text, but the 'clear' parameter is available. Overall, the behavior is transparent enough given the simple action.

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 without any redundant information. It is well-structured and directly states the tool's function.

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

Completeness5/5

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

For a simple input action, the description and schema provide all necessary information to invoke the tool correctly. There are no missing details about preconditions, return values, or side effects that would hinder an 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?

The schema already provides clear descriptions for all four parameters (element_id, text, by_js, clear), achieving 100% coverage. The description adds no extra detail beyond the schema, so it meets the baseline but does not enhance understanding further.

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: to input text into an input box element. This is a specific verb-resource combination that distinguishes it from sibling tools like element_click, element_hover, and element_select.

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 description provides no explicit guidance on when to use this tool versus alternatives, such as element_click or element_select. However, the name and description imply usage for entering text into input fields, which is clear enough for an agent to infer.

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