blink artifact

Set share link

share_link

Turn the share link of an artifact you own on or off (owner only). New artifacts are private: only the owner and invited people can open them. Call this only when the user asks to share the artifact by link; never turn a link on without the owner's consent. role is view, comment or edit (anyone with the link gets that role), or null to turn the link off. Password and expiry are kept. Returns { id, url, linkRole }.

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": {
      "id": "<id>",
      "role": "<role>"
    },
    "name": "share_link"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`role`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations, it discloses owner-only authorization, default privacy of new artifacts, consent requirements, role behavior for anyone with the link, and that password/expiry settings are preserved. It also describes the return shape, making the mutation's effects and constraints clear.

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 compact and front-loads the core action before adding privacy context, call conditions, role details, preservation behavior, and return values. Every sentence contributes useful 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?

For a two-parameter mutation tool with no output schema, the description supplies the important authorization, consent, role, preservation, and return-value context. An agent has enough information to invoke it correctly.

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?

With 0% schema description coverage, the description carries the burden and explains role thoroughly: view/comment/edit determine link access, and null turns the link off. The id parameter is only implicitly characterized as the artifact the caller owns, so one small semantic gap remains.

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?

The description states a specific verb and resource: turning an artifact's share link on or off, with owner-only scope and role semantics. It is clear what the tool does, though it does not explicitly name a sibling tool such as share_expiry as the alternative.

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?

It gives explicit usage conditions: call only when the user asks to share by link, and never enable a link without owner consent. It also states owner-only access, but it does not name a specific alternative tool for related operations like expiry management.

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

All blink artifact 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.

Resources

Need Help?