blink artifact

Set share expiry

share_expiry

Set or clear when shared access ends (owner only). expiresAt is an ISO 8601 time in the future, or null to clear. Without email it targets the share link (the link must be on); with email it targets that member, or that email's pending invite. Returns { id, target: link|member|invite, email?, expiresAt }.

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>",
      "expiresAt": "<expiresAt>"
    },
    "name": "share_expiry"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`email`	No
`expiresAt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only say readOnly=false and destructive=false, so the description carries the real burden and does well: it declares owner-only authorization, a precondition (link must be on), the pending-invite fallback, and the null-to-clear mutation semantics. It stops short of saying what happens if the id is wrong or whether clearing affects existing member access records.

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 compact sentences: action and permission scope first, the key parameter contract second, target dispatch and return shape last. No filler, nothing repeated from the schema.

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?

No output schema exists, and the description supplies the return shape itself ({ id, target, email?, expiresAt }), plus auth and precondition context for a mutation tool. The unresolved meaning of 'id' is the one gap an agent would still hit.

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 coverage is 0%, so the description must compensate. It fully specifies expiresAt (ISO 8601 future timestamp, or null to clear) and explains the optional email's dispatch behavior, but never says what 'id' identifies (artifact, share, or link), leaving one required parameter ambiguous.

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 concrete verb pair (set/clear) on a concrete resource (share expiry) and immediately scopes it with '(owner only)'. An agent can separate this from share_link, the closest sibling, without opening the schema.

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 explicit conditional routing: no email targets the share link (and requires the link to be on); email targets that member or a pending invite for that address. What is missing is a pointer to the sibling that creates the link when the 'link must be on' precondition fails.

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?