Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Lnk.Bio profile links

lnk_bio_profile_links_list
Read-onlyIdempotent

List a Lnk.Bio profile's links, including groups, badges and block links, with cursor-based pagination for up to 200 links per page.

Instructions

List a Lnk.Bio profile's links with a cursor, up to 200 per page, including groups, badges and block links. Requires handle. Returns a list (use cursor when paginated).

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_links_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoLinks per page, 1 to 200. Default: 100.
cursorNoCursor from `page.nextCursor` of the previous response. Start without one; it only works for the same handle.
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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context: pagination size (up to 200 per page), the fact that a cursor drives subsequent pages, and that responses include nested groups, badges and block links rather than bare 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 tight sentences, front-loaded with what is returned and the page cap, followed by the requirement and pagination note. Nothing is redundant with the schema and no sentence is filler.

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 read-only paginated list with full schema coverage and no output schema, the description supplies what an agent needs: return contents, page limits, and cursor mechanics. Only the sibling differentiation is missing, which keeps it short of a 5.

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 `limit`, `cursor`, and `handle` are already fully documented in the schema, including the cursor's same-handle constraint and default of 100. The description only restates the `handle` requirement and the cursor usage, adding no meaning beyond the schema — the baseline 3 applies.

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?

States a specific verb and resource ('List a Lnk.Bio profile's links') plus the scope of what's included (groups, badges, block links) and the page cap. It does not, however, distinguish itself from the sibling lnk_bio_profile_links_search, so an agent still has to infer which list variant to pick.

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?

The description notes the `handle` requirement and when to pass a cursor ('use cursor when paginated'), which is invocation guidance rather than selection guidance. It never says when to choose this over lnk_bio_profile_links_search or lnk_bio_profile_get, leaving alternatives implicit.

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