Put It Online

Upload a file

upload_file

Put a file online and get a short public link. Pass text directly, or base64 with encoding="base64" for binary files (images, PDFs, zips). An .html file becomes a web page; a .zip containing index.html becomes a website. Returns the URL, expires_at and a manage_token (shown once; anonymous callers need it to check or delete the link). Status may be "checking"/"publishing" (call get_link before sharing) or "unpublished" (not published). Limit 20 MB inline; use create_upload_session for bigger files.

Input Schema

Name	Required	Description	Default
`slug`	No	Custom link name (3-40 letters, digits, dashes); available on plans with custom names.
`content`	Yes	File content: plain text, or base64 when encoding is "base64" (use base64 for any binary file).
`encoding`	No	How `content` is encoded.	text
`filename`	Yes	File name including extension, e.g. "report.pdf" or "index.html". The extension decides how the link renders.
`password`	No	Visitors must enter this password to open the link; available on plans with password protection.
`mime_type`	No	Optional MIME type; used to add a missing file extension.

Output Schema

Name	Required	Description
`url`	Yes	The public link to share.
`kind`	Yes	html \| site \| file \| bundle \| pending
`slug`	Yes
`title`	Yes
`views`	Yes	View count; null when the link's account plan has no view counts, or the link has no account.
`status`	Yes	checking = not live yet (poll get_link); live = shareable; unpublished = not published; publishing = will be live soon (poll get_link); in_review = not available right now; removed = removed by moderation (see removed_reason, appeal_url).
`permanent`	Yes
`appeal_url`	No	Only with status removed: mailto link to appeal to abuse@putit.online.
`created_at`	Yes
`expires_at`	Yes	ISO time the link stops working; null for permanent links.
`file_count`	Yes
`manage_url`	No	Private page to manage/delete the link. Only returned on creation; keep it secret.
`size_bytes`	Yes
`content_url`	No	Only when live, for sites and single files: where the content itself is served (https://<slug>.putitcdn.com/…). Share `url` instead; it always works.
`checkout_url`	No	Only with status unpublished: the page where the uploader can publish this link.
`manage_token`	No	Secret token returned on creation for every new link (keep it secret). Anonymous callers pass it to get_link/delete_link; a link in an account is managed by that account instead.
`removed_reason`	No	Only with status removed: why, in plain words.
`status_message`	Yes
`removed_category`	No	Only with status removed: the moderation category (malware, phishing, explicit, …); null when not disclosed.
`password_protected`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

changedOutput schema / properties / manage_token / description

Previous value: -"Secret token for get_link/delete_link without an account. Only returned on creation."New value: +"Secret token returned on creation for every new link (keep it secret). Anonymous callers pass it to get_link/delete_link; a link in an account is managed by that account instead."

Changed1 schema field changedOct 18, 2026

addedOutput schema / properties / content_url

Added value: +{
+  "description": "Only when live, for sites and single files: where the content itself is served (https://<slug>.putitcdn.com/…). Share `url` instead; it always works.",
+  "type": "string"
+}

First observedOct 11, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations declare a non-idempotent, non-destructive write; the description goes well beyond them by disclosing the 20 MB inline limit, the one-time manage_token, the possible "checking"/"publishing"/"unpublished" statuses, and the returned fields. This is exactly the behavioral context an agent needs before calling a write tool.

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?

Front-loaded with the core action and link result, then layered with encoding, rendering, return value, status, and size limit in a dense but waste-free sequence. Every sentence carries actionable information.

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?

Despite an output schema existing, the description helpfully names the key returns (URL, expires_at, manage_token) and covers limits, status handling, and the sibling for large files. Nothing an agent needs to invoke it correctly 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?

Schema coverage is 100%, so the schema already documents each parameter. The description still adds real meaning beyond it: base64 for binary files, and the rendering semantics of filename extensions (.html becomes a web page, .zip with index.html becomes a website), plus the inline size ceiling.

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?

"Put a file online and get a short public link" states a specific verb and resource, and the description distinguishes this from create_upload_session (bigger files) and get_link (status checks). An agent can tell it apart from its siblings without opening their schemas.

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?

Explicit routing: use create_upload_session for files above 20 MB, and call get_link when status is "checking"/"publishing". It also notes the manage_token requirement for anonymous callers to check or delete. When-to-use and when-to-use-something-else are both present.

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

All Put It Online tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.