Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Lnk.Bio profile links

lnk_bio_profile_links_search
Read-onlyIdempotent

Search a single Lnk.Bio profile's links by handle and query to find matching items, returning up to 30 results with a visible cap flag and no paging.

Instructions

Search inside one Lnk.Bio profile's links, up to 30 matches, with a visible cap flag and no paging. Requires handle and query. Returns a list.

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>",
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "lnk_bio_profile_links_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesRequired. Text to search for inside one profile's links, 1 to 100 characters, e.g. `draft`.
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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so safety is covered. The description adds genuinely useful behavior: a hard 30-match cap, a 'visible cap flag', and no paging — but it never says what that flag looks like or that results are truncated/ranked, so the disclosure is partial. Call it 3.

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?

Three short sentences, front-loaded with the action and scope, with the cap/paging constraint in sentence one. 'Returns a list' is slightly redundant given the search framing but cheaply signals return shape; no real waste.

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 search with no output schema, the description covers scope, result cap, and absence of paging, which are the facts an agent needs to interpret results. It omits any hint about the conversation_id handshake and the fact that the cap flag means results may be incomplete, 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description restates that handle and query are required but adds nothing for context, llm_model, or conversation_id. It does reinforce the required-pair contract in one clause, so 4 is fair.

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 ('Search') and resource ('one Lnk.Bio profile's links') with bounding scope (up to 30 matches, no paging). It implicitly contrasts with lnk_bio_profile_links_list by emphasizing search-inside-one-profile, but never names that sibling to make the distinction explicit.

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 implied by 'Search inside one Lnk.Bio profile's links', and the 30-match cap hints that enumeration needs a different tool. However, there is no explicit when-to-use vs when-not guidance and no named alternative such as lnk_bio_profile_links_list or lnk_bio_profile_get.

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