Skip to main content
Glama
Edge DevTools MCP

Edge DevTools MCP

by syunnrai123

edge_type_text

Types text into the input field matching a CSS selector, enabling automated form filling and browser-based text entry.

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

Input Schema

NameRequiredDescriptionDefault
textYes要输入的文本
selectorYesCSS选择器

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/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 behavioral burden and does very little with it. It does not say whether existing text is cleared or appended, whether focus is set first, whether key events are dispatched, whether the element is waited for, or what happens if the selector matches nothing.

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?

One short sentence with no wasted wording, and the core action is front-loaded. But the brevity here reflects under-specification rather than efficiency — for a browser-automation mutation the sentence is too thin to earn its place as the only guidance.

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?

There are no annotations and no output schema, so the description is the only place to learn about side effects and failure modes, and it says nothing about them. For a UI-mutating action like typing into a page element, this leaves significant gaps around focus, clearing, event dispatch, and errors.

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?

Schema description coverage is 100% — both 'selector' (CSS选择器) and 'text' (要输入的文本) are documented in the schema. The description adds no extra meaning such as selector scoping rules, escaping, or multi-element resolution behavior, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrasing '在输入框中输入文本' states a concrete verb (输入/type) and resource (文本 into an input box), so the basic action is graspable. However, the tool actually targets an arbitrary element via CSS selector, not necessarily an 'input box', and nothing distinguishes it from siblings such as edge_click_element or edge_evaluate, which are the natural alternatives for interacting with a page.

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?

The description gives no when-to-use guidance, no prerequisites (element must exist / be focused / be visible), and no mention of alternatives like edge_evaluate or edge_dom_query. The agent must infer usage entirely from the tool name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.