own.page

Add a link

add_link

Add any URL and get the right widget automatically, like pasting a link in the editor: YouTube/Vimeo videos become players, Spotify/SoundCloud/Apple Music/Deezer become music players, Instagram/TikTok/X/YouTube channel/Twitch/Discord/Behance/LinkedIn/Threads/Patreon… profiles become rich profile cards, GitHub profiles show contributions, phone numbers become call links, other sites become links with their preview image. Prefer this over add_widget for anything that is a URL.

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": {
      "url": "<url>"
    },
    "name": "add_link"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	The link, e.g. "https://youtube.com/watch?v=…" or "instagram.com/name".
`page`	No	Which page: "home" (the default) or a subpage slug from list_pages.
`size`	No	Tile size on the 8-column desktop grid: small 2×2 (quarter row), wide 4×2 (half row), tall 2×4, large 4×4, banner 8×2 (full row). Phones use a 4-column grid, so wide/large/banner fill the phone width.
`title`	No	Optional button title (links and profile cards only).
`position`	No	Where it goes in reading order: "top", "bottom" (default), "after:<widget id>" or "before:<widget id>". "top" puts it right under the name and bio.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare the mutation is non-read-only, open-world, non-idempotent, and non-destructive. The description adds useful behavior beyond that: URL-type detection and the resulting widget categories, including generic preview links for other sites. It does not cover invalid URLs, duplicate behavior, or required permissions.

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?

The core behavior is front-loaded in the first clause, and the examples illustrate the auto-conversion rule. The platform list is long and slightly encyclopedic, but it is not padded with generic prose.

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?

For a five-parameter mutation tool with rich annotations and full schema coverage, the description covers purpose, behavior, and the sibling alternative well. However, it does not say what the tool returns or mention prerequisites/error cases, which is a notable gap because there is no output schema.

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 100%, so page, size, title, and position are already documented in the input schema. The description reinforces that the core input is a URL but adds no syntax or default details beyond the schema. Baseline 3 applies.

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 gives a specific verb ('Add') and resource ('any URL'), then states the automatic widget mapping. It explicitly distinguishes itself from add_widget, so an agent can identify it 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?

It gives a clear routing rule: prefer this over add_widget for anything that is a URL. It does not spell out prerequisites such as needing an existing page, or explicitly state the non-URL case, so it is strong but not exhaustive.

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

All own.page 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?