Skip to main content
Glama

upload_file

Upload local files or URLs to kie.ai and get a public URL for use with generation tools. Supports images, audio, video with base64 or direct URL input.

Instructions

Upload a file to kie.ai and get a public URL back. Use this to upload local images/audio/video before passing them to generation tools. Supports URL upload, base64 upload. Files expire after 3 days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_urlNoURL of file to upload — must be PUBLICLY reachable by kie.ai servers (no localhost/private IPs, no auth-gated or expired links). For local files use base64_data
file_nameNoCustom filename (optional)
base64_dataNoBase64-encoded file data — raw base64 or a full data: URI. Whitespace and base64url are normalized and the data:<mime>;base64, prefix is stripped automatically (its MIME infers the extension if file_name is omitted). NOTE: very large images can be truncated when passed as a tool argument — if you get a length/invalid error, prefer file_url with a public URL.
upload_pathNoStorage directory (e.g. "images", "audio", "video")uploads
Behavior3/5

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

No annotations provided, so description must carry behavioral disclosure. It mentions URL and base64 upload support, and 3-day expiry, but omits size limits, security, and deletion behavior beyond expiry.

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?

Three sentences: front-loaded with core function, followed by usage and capabilities. No wasted words.

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?

Covers purpose, usage, and expiry. Lacks error handling details, but for a simple upload tool with no output schema, the return ('public URL') is sufficiently implied.

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%, so baseline is 3. Description adds overall context but no parameter-specific meaning beyond schema descriptions.

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?

Clearly states the verb 'upload' and resource 'file to kie.ai', resulting in a public URL. Distinguishes from most siblings which are generation tools, but does not explicitly differentiate from 'upload_extend_audio'.

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?

Explicitly says 'Use this to upload local images/audio/video before passing them to generation tools', providing clear context. However, it does not mention when not to use or alternatives like 'upload_extend_audio'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/elibarnett/kie-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server