Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Lnk.Bio profile

lnk_bio_profile_get
Read-onlyIdempotent

Retrieve a Lnk.Bio profile's identity, bio, avatar, social icons, page tabs, and main-page links by handle to review or analyze a creator's public page.

Instructions

Get a Lnk.Bio profile's identity, bio, avatar, social icons, page tabs and main-page links. Requires handle.

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": {
      "handle": "<handle>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "lnk_bio_profile_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesRequired. lnk.bio handle, case preserved, e.g. `sportsillustrated`, `Curate.in`, `S&S` or `@brastel.thai`. A percent-encoded handle is accepted in the public path.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds the scope of the returned content (a single profile plus its main-page links), but says nothing about error behavior for a nonexistent handle or whether the links portion is truncated or paginated.

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?

Two short sentences, front-loaded with the payload description and ending with the precondition. No filler; the only near-waste is repeating that handle is required, which the schema already enforces.

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?

With no output schema, the description usefully enumerates the returned fields, and annotations cover the safety/idempotency profile. The remaining gap is failure and pagination behavior for a read against public handles, which is minor but non-zero.

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 handle field already documents format, casing, examples and percent-encoding, so "Requires `handle`" merely restates what the schema marks as required. Baseline 3 applies when the schema carries the parameter detail.

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?

Specific verb+resource ("Get a Lnk.Bio profile") with an enumerated payload: identity, bio, avatar, social icons, page tabs and main-page links. The "main-page links" qualifier implicitly separates it from lnk_bio_profile_links_list and links_search, though neither sibling is named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is "Requires `handle`," which is a precondition rather than a when-to-use rule. Nothing tells the agent when to choose this over lnk_bio_profile_links_list, lnk_bio_profile_links_search, or lnk_bio_profiles_list, and no exclusions or edge cases (unknown handle, private profile) are stated.

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

Deploy Server

Other Tools