Skip to main content
Glama

Get a photo upload link

get_upload_link

Creates a one-time web page where the owner adds photos from their phone (JPEG, PNG or WebP, up to 15 MB each, 20 photos, valid for 30 minutes; location and camera details are removed from every photo). Uploaded photos get asset ids, which list_photos returns and which gallery sections and the theme logo use.

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": {
      "site_id": "<site_id>"
    },
    "name": "get_upload_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site id from list_sites or create_site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and idempotentHint=false; the description goes well beyond by disclosing that the link is one-time, expires in 30 minutes, and that location/camera metadata is stripped from every photo. It also gives concrete acceptance limits (JPEG/PNG/WebP, 15 MB each, 20 photos), which an agent needs to set caller expectations and avoid promising results the tool cannot deliver.

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?

A single dense sentence, but it is front-loaded with the core action and the parenthetical constraints are organized rather than scattered. Trimming is possible, yet essentially every clause (limits, expiry, metadata stripping, asset id outcome) carries information an agent would otherwise lack.

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?

With no output schema, the description does most of the return-value work by explaining that uploaded photos receive asset ids consumed by list_photos, gallery sections, and the theme logo. The one remaining ambiguity is that it never explicitly states the immediate response is the link/URL itself, leaving the caller to infer the return shape.

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?

Only one parameter (site_id) exists and the schema already documents it at 100% coverage, including where the id comes from. The description adds no parameter-level meaning, which is acceptable given the schema baseline but earns no extra credit.

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 concrete verb and artifact: 'Creates a one-time web page where the owner adds photos from their phone.' The 'one-time web page for phone uploads' framing is distinct in the sibling set from link-retrieval tools like get_preview_link or photo-management tools like list_photos/update_photo, so an agent can identify the operation without opening the 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?

Usage context is clear: this is the path for getting photos from the owner's device onto the site, and the closing sentence names the downstream consumers (list_photos, gallery sections, theme logo), which tells the agent why it would call this. There are no explicit exclusions or named alternatives, so it stops short of a 5.

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.

Resources