Alto

Make a recipient link

create_link

Make a tracked link to a video for one person, so every view is tied to them. Returns the link's URL to paste into an email.

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": {
      "videoId": "<videoId>",
      "name": "<name>"
    },
    "name": "create_link"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Who it's for, e.g. "Michelle Barba".
`note`	No	A personal note shown on their demo page.
`email`	No
`title`	No	Their job title.
`company`	No
`videoId`	Yes
`expiresInDays`	No	Days until the link stops working; null never expires; left out uses the workspace default.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 9, 2026

changedInput schema / properties / name / description

Previous value: -"Who it's for, e.g. \"Dana Whitfield\"."New value: +"Who it's for, e.g. \"Michelle Barba\"."

First observedOct 1, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=false, so the mutation and non-idempotent profile is covered structurally. The description adds the return shape ('returns the link's URL'), useful since there is no output schema, but says nothing about permissions, duplicate-call behavior, or expiry defaults.

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?

Two tight sentences with no filler; the purpose is front-loaded and the return value is appended where it belongs. Every clause earns its place.

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?

For a 7-parameter creation tool with no output schema, the description covers purpose and return value but leaves the recipient-identity parameters (email, title, company) and the non-idempotent, expiring behavior unexplained. It is adequate but not complete for the tool's 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 coverage is 57%, so the schema documents name, note and expiresInDays while email, title, company and videoId carry no descriptions. The description only hints at the name/videoId pairing ('for one person', 'to a video') and adds nothing about the undocumented recipient fields, so it does not compensate for the gap.

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 ('Make') plus resource ('a tracked link to a video') and a scoping qualifier ('for one person') that separates it from list_links and the upload siblings. The additional 'every view is tied to them' clause clarifies the tracking semantics in one phrase.

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?

The description implies the use case ('paste into an email'), which is enough to infer personalized outreach links, but it never states when to prefer this over siblings like list_links or create_upload, nor any prerequisites or exclusions. Usage is implied rather than guided.

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

All Alto 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?