Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Lnk.Bio profiles

lnk_bio_profiles_list
Read-onlyIdempotent

Lists public Lnk.Bio profiles with last-modified time and priority; use cursor pagination and modifiedSince to fetch profiles updated after a date, continuing even when a page is empty.

Instructions

List public Lnk.Bio profiles with last-modified time and priority; an empty page can still have more. Optional inputs: cursor, limit and modifiedSince. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "lnk_bio_profiles_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoProfiles per page, 1 to 500. Default: 100.
cursorNoCursor from `page.nextCursor` of the previous response. Start without one; a page can be empty while `page.hasMore` is true, so keep following it. It only works for the same `modifiedSince` filter.
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.
modifiedSinceNoOnly profiles last modified at or after this time, as an ISO 8601 date or time (such as `2026-01-31`) or epoch seconds; no zone means UTC. A page can be empty while `page.hasMore` is true; follow `page.nextCursor`.
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, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations by warning that an empty page can still have more and that the return value is a list.

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?

The description is two compact sentences with no wasted wording. It front-loads the core purpose and then follows with the pagination caveat and optional inputs.

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 six-parameter list tool with full schema coverage and no output schema, the description gives enough context: what is listed, what is returned, and how pagination behaves. It could be slightly more complete by distinguishing this tool from related profile and link tools, but the essentials are present.

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 the schema already documents cursor, limit, and modifiedSince thoroughly, including pagination nuances. The description names the optional inputs but adds little meaning beyond what the schema provides, so 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?

The description states a specific verb and resource: 'List public Lnk.Bio profiles.' It also notes the fields returned (last-modified time and priority), but it does not explicitly differentiate this from sibling tools such as lnk_bio_profile_get or lnk_bio_profile_links_list.

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 gives useful pagination guidance ('use cursor when paginated') and warns that an empty page can still have more results. However, it does not say when to use this list tool instead of related sibling tools like lnk_bio_profile_get or lnk_bio_profile_links_search.

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