Page Lemon

Get an upload link

create_upload_link

Destructive

Returns a 1-hour link where the user uploads photos and files into a site folder; each upload goes live at once as a new version (get_site lists them). replace_site, only when the user asks: a zip that replaces every file.

Input Schema

Name	Required	Description
`site`	Yes
`folder`	No	Target folder (default images); not with replace_site
`site_token`	No	From an anonymous deploy (secret)
`replace_site`	No	true: a one-use link for a whole-site zip

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026

changedInput schema / properties / replace_site / description

Previous value: -"true: a one-use link for a zip that replaces the whole site"New value: +"true: a one-use link for a whole-site zip"

addedInput schema / properties / site_token / description
```
Added value: +"From an anonymous deploy (secret)"
```

Changed1 schema field changedOct 25, 2026
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "type": "object"
+}
```
Changed2 schema fields changedOct 22, 2026
- removedInput schema / properties / site / description
```
Removed value: -"Site name"
```
- removedInput schema / properties / site_token / description
```
Removed value: -"From the first deploy (no account)"
```

Changed3 schema fields changedOct 21, 2026

changedInput schema / properties / site / description

Previous value: -"Site name, e.g. brave-otter-4821"New value: +"Site name"

changedInput schema / properties / site_token / description

Previous value: -"site_token from the first deploy (anonymous sites only)"New value: +"From the first deploy (no account)"

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": {},
-  "properties": {
-    "agent_message": {
-      "type": "string"
-    },
-    "confirm_token": {
-      "type": "string"
-    },
-    "error": {
-      "description": "On failure (isError): {code, message}"
-    }
-  },
-  "type": "object"
-}New value: +null

AddedOct 15, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the destructive and open-world annotations, it discloses the 1-hour link expiry, immediate publishing as a new version, and that replace_site uses a zip that replaces every file. These are important behavioral consequences that help the agent reason about destructive scope and timing.

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?

The core behavior, expiry, immediate-version effect, and replace_site caveat are front-loaded and waste no words. The parenthetical get_site reference earns its place by clarifying where uploaded versions appear.

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?

With annotations declaring destructive/open-world behavior, an output schema, and strong schema descriptions, the description supplies the remaining context an agent needs: timing, immediate versioning, and the replace_site condition. No essential decision information is missing.

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?

The schema already covers 75% of parameters, and the description adds useful meaning for replace_site and its relationship to folder behavior. It does not explain site_token, but that parameter is documented in the schema, so the description adds value without needing to duplicate everything.

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 states a specific resource and action: a 1-hour link for uploading photos/files into a site folder, with a distinct replace_site mode. It clearly distinguishes upload-link behavior from listing via get_site and from whole-site replacement, so an agent can identify the tool 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?

It gives an explicit conditional rule for replace_site: use it only when the user asks. It also implies the default upload-link use case and references get_site for listing versions, though it does not enumerate other alternatives beyond the two modes.

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

All Page Lemon tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?