Skip to main content
Glama

Change link settings

update_link
Destructive

Change who can open a link, its title, its link name (a readable address like artifactsend.com/d/praxis-portfolio, Brand plan on the space that owns the link), expiry or notifications, or turn it off.

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": {
      "link": "<link>"
    },
    "name": "update_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesThe link: its URL, slug, id or title.
allowNoOnly these emails or domains can open it, e.g. ["@sequoiacap.com", "dana@acme.com"].
titleNo
accessNopublic: anyone with the link. email: reader types an email (fake and throwaway addresses are refused). verified: reader proves the email, with Google or a 6-digit email code.
folderNoPut it in this folder on my Files page, by name. Made if it does not exist. Leave out to keep it outside folders.
notifyNoEmail me when someone opens it the first time. Default true.
disabledNo
downloadsNoReaders get a Download button for a PDF, Office file, image or video. Default false.
link_nameNoA readable address: 3 to 48 lowercase letters, numbers and dashes, e.g. praxis-portfolio. Empty string removes it. The short address keeps working.
ai_readingNoWhat a reader's own AI (Claude, ChatGPT) may take. questions (default): only the parts that answer each question, so I see every question and no full copy leaves. full: the whole text, marked with the reader's email. off: no AI reading.
expires_in_daysNoClose the link after this many days.
discourage_screenshotsNoBlur the page when the reader switches away, block printing and copying, and watermark it with their email. No website can fully stop a screenshot. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / link_name
      Added value: +{
      +  "description": "A readable address: 3 to 48 lowercase letters, numbers and dashes, e.g. praxis-portfolio. Empty string removes it. The short address keeps working.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / folder / description
      Previous value: -"Put it in this folder on my Artifacts page, by name. Made if it does not exist. Leave out to keep it outside folders."New value: +"Put it in this folder on my Files page, by name. Made if it does not exist. Leave out to keep it outside folders."
  3. Changed2 schema fields changed
    • addedInput schema / properties / discourage_screenshots
      Added value: +{
      +  "description": "Blur the page when the reader switches away, block printing and copying, and watermark it with their email. No website can fully stop a screenshot. Default false.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / downloads
      Added value: +{
      +  "description": "Readers get a Download button for a PDF, Office file, image or video. Default false.",
      +  "type": "boolean"
      +}
  4. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the mutation and exposure profile is covered structurally. The description adds the useful nuance that settings can be changed or the link turned off, but it does not explain what is actually destroyed or irreversible (e.g. whether clearing link_name breaks old addresses, whether removing allow lists exposes the link publicly). With annotations carrying the safety signal, this is adequate but thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with no filler, and the mutable fields come before the "turn it off" clause. The embedded parenthetical about link name is a bit convoluted and partly duplicates the schema, but overall it stays tight and scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a 12-parameter mutation tool with no output schema, so the description needs to do real work. It enumerates the changeable surface but leaves out permission requirements, reversibility, what the response contains, and what happens to untouched settings — meaningful gaps for a destructiveHint=true tool at this complexity.

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 83%, so the schema already documents nearly every parameter, including enum meanings for access and ai_reading. The description mostly restates those categories (access, title, link name, expiry, notifications, disabled) rather than adding syntax, defaults, or interaction rules between them — for example how access interacts with allow. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

A specific verb ("Change") plus the resource (a link's settings), followed by the exact surfaces that can be changed: access, title, link name, expiry, notifications, disabled. An agent immediately knows this is a mutation of an existing link, not creation or reading. It stops short of naming a sibling to prefer for adjacent jobs (e.g. update_artifact, set_brand), so it is clear but not sibling-differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the enumerated settings — you call it when you want to alter one of them — and "or turn it off" hints at the disable path. There is no explicit when-not guidance, no statement that the link must already exist, and no pointer to alternatives such as update_artifact for non-link artifacts.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources