Put It Online

Extend a link

extend

Restart an expiring link's expiry clock (also brings back a recently expired link). Permanent links are unaffected. Requires a connected account whose plan includes extending.

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

Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent mutation, so the bar is lower; the description adds real value by explaining what happens (expiry clock restarts, expired links return) and what is untouched (permanent links), plus a plan-level prerequisite. It omits rate-limit or repeated-call behavior, but covers the mutation's effect well.

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?

Three short sentences, front-loaded with the action, then the effect, then the eligibility constraint. Each sentence carries distinct information with no repetition or filler.

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?

An output schema exists, so return values need not be described. The description covers the action, its effect on expired vs permanent links, and the account/plan prerequisite — everything needed to invoke an annotated mutation 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?

Only one parameter, and schema coverage is 100% with an example format ('k3x9pq' or a full URL). The description adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 specific verb and resource ('extend', "link's expiry clock") and clarifies scope: it applies to expiring/recently expired links only. The note that 'Permanent links are unaffected' implicitly separates it from the sibling make_permanent, so an agent can route correctly without opening schemas.

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 a clear precondition ('Requires a connected account whose plan includes extending') and an exclusion ('Permanent links are unaffected'), which tells the agent when this tool is not the right choice. It does not explicitly name make_permanent as the alternative for permanent links, so it stops just short of full routing guidance.

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.