Skip to main content
Glama

Upload Image

upload_image
Destructive

Uploads a local image file to BGRemover Video and returns a CDN URL for use as image_url or media_url in other BGRemover Video tools.

Instructions

This tool will upload a local image file to BGRemover Video and return a CDN URL that can be passed as image_url or media_url to another BGRemover Video tool. It takes one argument: - file_path (str, required): Absolute local path to the image file.

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": {
      "file_path": "<file_path>"
    },
    "name": "upload_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesAbsolute local file path to the image to upload (e.g. '/Users/me/Downloads/photo.png').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true, destructiveHint=true and idempotentHint=false, so the description's job is to add context beyond those flags; it adds that a remote CDN URL is created and is reusable by other tools, which is genuinely useful. However, it never explains why the operation is flagged destructive, whether repeated uploads create duplicate remote artifacts, or whether there are size/format limits, leaving the agent without guidance on the risks the annotations advertise.

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 key value proposition (produces a CDN URL usable by other BGRemover Video tools) is front-loaded in the first clause. The trailing "It takes one argument: - file_path..." bullet is pure duplication of the schema and could be cut, but the overall length is short and easy to scan.

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

Completeness4/5

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

There is no output schema, and the description correctly compensates by stating the return value (a CDN URL) and its intended downstream use. For a one-parameter upload tool this is nearly complete; only failure modes and upload constraints are absent.

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 coverage is 100% and the schema already documents file_path as an absolute local path with an example. The description's line "file_path (str, required): Absolute local path to the image file" restates that exactly without adding format restrictions or path-resolution behavior, so the baseline 3 for high-coverage schemas applies.

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?

The description names a specific verb and resource ("upload a local image file") and goes further to state the outcome (a CDN URL) and that the returned URL is meant to be passed as image_url or media_url to another BGRemover Video tool. This makes the image-vs-video split from upload_video unambiguous without needing to open 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?

It gives clear positive context: call this first to get a hosted URL, then feed that URL into other tools. It never states exclusions or prerequisites (allowed formats, size limits, or "use upload_video for video files"), so the agent must infer the boundary with the sibling upload tool.

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