Sharelint

Check link preview

check_link_preview

Read-onlyIdempotent

Check how a URL’s link preview (title, description, image) appears when shared on WhatsApp, Facebook, Messenger, Instagram, X (Twitter), LinkedIn, Telegram, iMessage, Discord, Slack, Snapchat and TikTok. Fetches the page as each app’s crawler, validates Open Graph and Twitter Card tags and the preview image (size, format, weight), and returns a score, per-app results and copy-ready fixes. Use it when a shared link shows no preview, the wrong image or title, or before sharing a page.

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": "check_link_preview"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Public http(s) URL or bare domain to check, for example "example.com/pricing". Private and local addresses are refused.
`crawler`	No	User-Agent to fetch the page as for share previews. Defaults to Facebook’s crawler, which most apps resemble.	facebook

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safe, idempotent read profile, and the description adds real substance beyond them: it fetches the page as an app crawler, validates Open Graph and Twitter Card tags, checks image size/format/weight, and returns a score plus copy-ready fixes. It does not mention rate limits or how long a check takes, and 'as each app's crawler' is slightly looser than the single-crawler parameter, but there is no annotation conflict.

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?

Front-loads the purpose, then behavior, then when-to-use in three tight sentences. The long platform enumeration is informative but is the one place that could be trimmed without much loss.

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?

With no output schema, the description carries the return-value burden and does so by naming the score, per-app results, and copy-ready fixes. Combined with the disclosed fetching and validation behavior and clear usage triggers, an agent has everything needed to call it correctly.

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 100%, so both url and crawler are already documented, including the private/local address refusal and the Facebook default. The description adds only a little context by implying which platforms resemble the default crawler, which is baseline-level value 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Check how a URL's link preview ... appears') and enumerates the concrete outputs (title, description, image) and target platforms. It is clearly distinguishable from check_url and check_app_links because it is explicitly about share-preview rendering across social apps.

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?

Provides explicit triggering conditions: 'when a shared link shows no preview, the wrong image or title, or before sharing a page.' It does not name sibling alternatives or state when not to use it (e.g., general page health vs. preview), so it falls short of full routing guidance.

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

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