Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

uploadRemoteFile

Downloads a file from a remote URL and stores it in TestingBot storage so remote assets are available for cloud browser, mobile, and app tests.

Instructions

Upload a file from a remote URL to TestingBot storage. The file will be downloaded from the URL and stored.

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": {
      "remoteUrl": "<remoteUrl>"
    },
    "name": "uploadRemoteFile"
  }
}

Input Schema

NameRequiredDescriptionDefault
remoteUrlYesRemote URL of the file to upload

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It states the mechanism (fetch then store) but says nothing about whether an existing file of the same name is overwritten, size or content-type limits, required credentials, or how the stored file is later referenced — all material for a write operation.

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?

Two short sentences, front-loaded with the action and destination. The second sentence largely restates the first ('downloaded from the URL and stored'), so a small amount of text does not earn its place.

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 simple single-parameter tool the description is minimally adequate, and the input schema is fully documented. However, with no output schema and no annotations, it omits the return value (file id/path?) and overwrite/auth behavior, leaving the agent unable to predict the result of calling it.

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?

With one parameter and 100% schema description coverage, the schema already defines remoteUrl as a URI. The description reinforces the source is a URL but adds no format, protocol, or length constraints beyond what the schema provides, so baseline 3 applies.

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 gives a specific verb and resource ('Upload a file ... to TestingBot storage') plus the source qualifier 'from a remote URL', which implicitly separates it from a local-file upload sibling. It stops short of naming uploadFile explicitly, so the differentiation is inferable rather than stated.

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?

There is no when-to-use guidance, no mention of the alternative uploadFile for local files, and no prerequisites such as whether the remote URL must be publicly reachable or authenticated. The agent must guess that this tool is the right choice when the file lives at a URL.

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