Put It Online

Keep a link online permanently

make_permanent

Idempotent

Turn an expiring link into a permanent one (uses one of the plan's permanent slots; see get_account). Requires a connected account whose plan includes permanent links.

Input Schema

Name	Required	Description	Default
`slug`	Yes	The link name, e.g. "k3x9pq" (a full https://putit.online/<name> URL also works).

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/5.0

Behavior4/5

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

Annotations already declare the mutation/idempotency/destructive profile, and the description adds two things they don't: the operation consumes one of the plan's finite permanent slots (a quota side effect) and it requires an eligible connected account. It still doesn't say what happens when slots are exhausted or whether the action is reversible.

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?

Two dense sentences that front-load the action and then the resource prerequisite; the cross-reference to get_account is inline and every clause carries information.

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 one well-documented parameter, a rich annotation set, an output schema, and an explicit account/plan precondition, the description is nearly self-sufficient. Only the edge case of slot exhaustion is left unaddressed.

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% for the single slug parameter, so the schema already documents format and accepted URL/name forms. The description adds no additional meaning about the parameter, which is the baseline case.

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?

States a specific verb+resource with scope: 'Turn an expiring link into a permanent one.' An agent can tell this is a one-way conversion rather than the time-window tweak implied by the sibling 'extend', though the description never names that sibling to make the contrast explicit.

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?

Gives clear preconditions (requires a connected account whose plan includes permanent links) and points to get_account for checking slot availability. It does not state when to prefer this over extend or what to do if no slots remain, so exclusions are absent.

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.