Skip to main content
Glama
Sign In
serve

serve

by servelink-swyftlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Update link TTL

update_ttl

Change the protection duration of a protected link without rotating its credentials. Set a new duration to recalculate expiration; only works with unexpired protection.

Instructions

Change the protection duration (TTL) of an already-protected link (Pro plan required) without rotating its credentials. The link must currently be protected with an unexpired credential; expired protection must be renewed first with renew_link. The expiration is recalculated from the new duration, not extended from the previous expiry.

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": {
      "label": "<label>",
      "ttl": "<ttl>"
    },
    "name": "update_ttl"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttlYesNew TTL duration (e.g. 48h, 7d).
labelYesLabel of the link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.6

TDQS

A4.7/5.0
Behavior5/5

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

The description goes beyond the basic annotations by explaining the precondition, the non-rotation of credentials, and the exact recalculation semantics (new duration, not extended from previous expiry).

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 description is concise and front-loaded, conveying the core action first and then adding necessary constraints and preconditions in only three sentences.

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?

Given the simple two-parameter input and no output schema, the description fully covers the necessary context: prerequisites, behavior, and an explicit alternative for expired protection.

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 both required parameters, and the parameter descriptions are clear. The main description adds context for TTL behavior but does not significantly expand on the parameter-level semantics.

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 clearly states a specific action: changing the TTL of an already-protected link, and distinguishes it from related operations by noting it does not rotate credentials and that expired protection must be renewed first.

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?

It explicitly states when to use this tool (for protected links with unexpired credentials) and when not to (expired protection should use renew_link). It also mentions the Pro plan requirement.

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

Deploy Server

Other Tools