Skip to main content
Glama
Brave Session MCP

Brave Session MCP

by MacStenk

brave_upload

Destructive

Select specified local files in a previously read file-upload field using a tab ID and element reference.

Instructions

Wählt ausdrücklich angegebene lokale Dateien in einem zuvor gelesenen Datei-Uploadfeld aus.

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": {
      "tabId": "<tabId>",
      "ref": "<ref>",
      "files": "<files>"
    },
    "name": "brave_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesElementreferenz aus brave_read für genau diesen Tab.
filesYes
tabIdYesStabile Tab-ID aus brave_tabs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare this as non-read-only, open-world, and destructive. The description adds that files are local and the target field must be previously read, but it does not explain what destructive effect may occur, whether files overwrite an existing selection, or whether the upload is submitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single efficient sentence with no redundant wording. It is front-loaded around the action and target, though its brevity leaves important behavior unstated.

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?

For a destructive, open-world file-upload action with no output schema, the description is too sparse. It omits key details such as whether the upload is triggered immediately, how existing selections are affected, allowed file types, and what happens after selection.

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 explains tabId and ref, and includes constraints for files. The description adds useful semantics that files are local and ref should refer to a previously read file-upload field, but it does not clarify file path formatting or the max-10 constraint.

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?

The description states a specific action and target: selecting explicitly named local files in a file-upload field. It is distinguishable from general click/fill/navigate siblings, though it does not explicitly contrast itself with any alternative.

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?

It gives an important precondition: the upload field must have been read beforehand. However, it does not state when not to use this tool, what alternatives exist, or any restrictions such as requiring a valid file input element.

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