MightyAutomation

Import a file from URL

import_file

Download a remote file (public https URL) into the workspace Media Assets library. Allowed types: image/, audio/, video/*, and application/pdf — text/html and other types are rejected; max 10 MB. Optionally attach a note to a contact recording that the file was imported for them.

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": {
      "url": "<url>"
    },
    "name": "import_file"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Public https URL of the file to import.
`name`	No	Display name for the asset (default: the remote filename).
`contact_id`	No	Optional — attach an import note to this contact.

Output Schema

Name	Required	Description
`ok`	No
`url`	No
`asset`	No
`error`	No	Present only when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare the write, open-world, non-idempotent, non-destructive profile, so the bar is lower. The description still adds real behavior: strict type filtering, a size limit, and a side effect (attaching an import note to a contact) that the annotations do not convey.

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?

Two dense sentences, front-loaded with the action and destination before the constraints and the optional side effect. No filler.

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?

An output schema exists, so return values need not be described. Types, size limit, rejection behavior, and the contact-note side effect are all covered, leaving nothing an agent needs in order to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description goes beyond the schema by explaining that contact_id causes an import note to be recorded against that contact, and it reinforces the URL constraint (public https) beyond the generic uri format.

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?

States a specific verb (download/import) and resource (remote file into the workspace Media Assets library), plus the accepted media types. An agent can distinguish it from list_media_assets, which only lists existing assets, without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete preconditions (public https URL, allowed MIME types, 10 MB cap) and explicit exclusions (text/html and other types rejected). It stops short of naming an alternative tool or telling the agent what to do when the file is local or oversized.

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

All MightyAutomation tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?