Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

set_file_input

Set files on an element via host paths using DOM.setFileInputFiles, enabling automated file upload testing in Electron debugging.

Instructions

Set files on an via DOM.setFileInputFiles (host paths)

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>",
      "files": "<files>"
    },
    "name": "set_file_input"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYes
selectorYes
targetIdNo
processIdNoProcess ID. If omitted, uses the single running app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations only declare destructiveHint=false, so the description must carry the rest. It usefully clarifies that `files` are host filesystem paths rather than content, which is genuine added behavior. It does not say whether existing selections are replaced or appended, whether the input must be visible/attached, or what failure looks like when the selector matches a non-file element.

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?

A single front-loaded sentence with no filler; the verb, target element, mechanism, and path semantics all appear immediately. Nothing is padded or repeated from the schema.

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

Completeness3/5

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

For a narrow four-parameter CDP wrapper with no output schema and thin annotations, the description covers the core intent but leaves real gaps: selector format, the role of `targetId`, and how multiple files behave. Adequate to attempt a call, not complete enough to call confidently in edge cases.

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 only 25% (only `processId` is documented), so the description should compensate more. It does add meaning for `files` (host paths, not payloads) and indirectly for `selector` (the target file input), but `targetId` is entirely unexplained in both schema and description, and the selector syntax (CSS vs. other) is never specified.

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

Purpose4/5

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

States a specific verb and resource ("Set files on an <input type=file>") and names the underlying mechanism (DOM.setFileInputFiles). An agent immediately knows this populates a file chooser input, but the description does not distinguish it from any sibling or clarify scope beyond file inputs.

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?

Usage is implied by the mention of `<input type=file>` — use it when a page needs a file attached to a file input. There is no explicit when-not guidance, no mention of prerequisites (e.g. whether the element must already exist or be in the DOM), and no note on what to do for drag-drop or non-file-input upload zones.

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