Skip to main content
Glama

Find a website's social media profiles

social_links
Read-only

Find a website's social media profiles: X/Twitter, LinkedIn, Facebook, Instagram, YouTube, TikTok, GitHub, Discord, Telegram, Medium, Reddit, Threads, Bluesky, Farcaster and more, from its links. Fast (1-3 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.002 per call (x402, USDC on Base).

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real behavioral detail beyond that: expected latency (1-3 s), a 20 calls/day free allowance, and a per-call price with the x402/USDC-on-Base payment mechanism. What's missing is any hint about the result shape (e.g., whether unmatched platforms are omitted or returned empty).

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 capability is front-loaded in the first clause, then cost/speed follow. It is a single dense sentence plus two short pricing sentences — efficient, though the pricing detail is somewhat verbose for a tool description and could be trimmed.

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 simple two-parameter read-only tool with a fully documented schema and no output schema, the definition covers purpose, cost, latency, and payment requirements. The notable gap is the return value: an agent can't tell from this whether it gets a mapping of platform to profile URL, a list, or confidence flags — and no output schema exists to fill that in.

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%, and the schema itself explains both url ('Public http(s) URL') and the x402 payment-signature flow, so the description needn't duplicate it. The description adds no parameter-level semantics beyond that — 'from its links' only loosely clarifies what kind of URL to supply. Baseline 3 applies 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?

The description opens with a specific verb+resource ('Find a website's social media profiles') and enumerates the platforms covered (X/Twitter, LinkedIn, Facebook, ...), plus the mechanism ('from its links'). This clearly separates it from sibling tools like links, feeds, or contacts, which don't promise platform-specific profile discovery.

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 context is present but indirect: the stated 1-3 s speed and the free-tier/cost model help an agent decide whether to spend a call. However, there is no explicit 'use this when...' guidance and no exclusions or pointers to alternatives (e.g., links for general link extraction).

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.