Skip to main content
Glama

CardScope Link Preview

check_link_preview

What X, LinkedIn, Slack, Discord, iMessage, Bluesky, Threads, Mastodon, WhatsApp, Telegram, and Teams will show for a URL. Returns the same JSON as GET /v1/preview, plus a short summary.

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

NameRequiredDescriptionDefault
urlYesAbsolute http or https URL
platformsNoPlatform ids to include, such as x or slack. Omit for all 11.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description bears full responsibility for behavioral disclosure. It discloses the return payload shape ('same JSON as GET /v1/preview, plus a short summary'), which is useful, but says nothing about whether the URL is fetched live, whether remote images are fetched, rate limits, auth requirements, or failure behavior on unreachable URLs.

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 sentences, no filler, with the scope (which platforms, what output) front-loaded. Nothing in it is padding.

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 two-parameter read tool this is nearly adequate, and the absence of an output schema is partially offset by the reference to GET /v1/preview. However, that reference points outside the definition, so an agent without access to API docs cannot know the actual response fields from this description alone.

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 the baseline is 3; both parameters are already documented in the schema, including 'Omit for all 11.' The description reinforces the platform set by listing the eleven service names, which helps map friendly names to platform ids, but adds no formatting or validation detail beyond the schema.

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 names the concrete resource (a URL's link preview) and enumerates the eleven platforms whose rendering it reports, which is far more specific than the tool name alone. It stops short of a clean verb phrase, leaning on 'Returns the same JSON as GET /v1/preview' to convey what the output is, so an agent must infer that this is a fetch/check operation.

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?

Usage is only implied: the enumerated platforms suggest 'use this when you want to know how a link renders across services.' There is no explicit when-to-use, when-not-to-use, or routing against the sibling list_platforms, though the purposes are distinct enough that an agent can likely separate them unaided.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources