Skip to main content
Glama

Dplooy

Upload media

upload_media

Pass public https URLs — base64 ONLY for images you generated yourself. Adds up to 16 images to the Media Library in ONE call (all plans; images only, max 5MB each). For any image that exists on the web, pass its URL; the Dplooy server downloads it directly. base64 is STRICTLY the fallback for images you generated yourself that exist nowhere on the web — NEVER base64-re-encode an image that has a URL. Batch ALL the site's images into one call, do not call once per image. Each image returns a stable public URL for tags plus the { mediaId, path } reference Data image cells need. Items succeed or fail independently. Upload images BEFORE writing the site's HTML. TIP: images the user already added to their Media Library are listed by list_media — reuse those URLs directly, no upload needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imagesYesUp to 16 images in ONE call — batch your uploads instead of calling once per image. Each image needs exactly one of url or base64. Items succeed or fail independently.

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description adds valuable behavioral detail: the server downloads URLs directly, items succeed or fail independently, each image returns a stable public URL plus mediaId/path, and limits are stated (images only, max 5MB each). No contradiction with annotations exists.

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 description is front-loaded with the primary instruction and every sentence carries operational weight. It is somewhat long and partially repeats schema-level details, but the added workflow and fallback rules justify the length.

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?

There is no output schema, yet the description discloses the return values (public URL plus mediaId/path), batching behavior, independent failure mode, and correct sequencing relative to site HTML generation. This is enough for an agent to invoke the tool correctly.

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 description coverage is 100% and the schema already documents url/base64/filename thoroughly, including 'ALWAYS FIRST' and 'STRICT FALLBACK'. The top-level description restates this guidance but adds little new parameter-level meaning beyond a clear prose summary.

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 opens with a specific action and scope: 'Adds up to 16 images to the Media Library in ONE call.' It clearly distinguishes this from siblings like list_media and delete_media by framing it as the creation/upload operation.

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

Usage Guidelines5/5

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

Usage guidance is explicit: use public URLs for web images, base64 only for self-generated images with no URL, never re-encode a URL image, batch all images into one call, and upload before writing HTML. It even points to list_media as an alternative when images already exist.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools are clearly separated by resource and action, and the descriptions are detailed enough to avoid most misselection. The main ambiguity is between deploy_files and deploy_website (both deploy a site, one multi-file and one single-file), and get_project versus get_project_files versus list_projects require careful reading.

Naming Consistency5/5

Every tool follows a consistent snake_case verb_noun pattern: create_*, get_*, list_*, delete_*, update_*, upload_*, assign_to_project, unassign_from_project, configure_chatbot. There are no camelCase names, vague verbs, or mixed conventions.

Tool Count2/5

At 29 tools, this exceeds the comfortable MCP surface and crosses into the 'too many' range. The breadth is somewhat justified by the number of subdomains (projects, files, forms, data, bookings, chatbot, media), but several getters and listers could be consolidated without losing capability.

Completeness4/5

The tool set covers a full website build lifecycle: account checks, content modeling, media upload, deploy, assignment, chatbot configuration, and post-deploy file edits. Minor gaps remain: booking pages and form settings are intentionally read-only via the MCP, and there is no chatbot deletion or teardown tool.

Resources