Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Linktree profile

linktree_profile_get
Read-onlyIdempotent

Fetch a public Linktree profile by handle to retrieve its links and social accounts. Use it to gather Linktree contact and link data for a given username.

Instructions

Get a public Linktree profile by handle, including links and socials. 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": "linktree_profile_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesRequired. Linktree handle to look up, with or without a leading @.
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. The description adds two useful behavioral facts beyond that: only *public* profiles are reachable, and the payload includes links and socials. It says nothing about failure behavior for unknown or private handles.

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 with the capability stated first and the prerequisite second; nothing is padded. The trailing 'Requires `handle`' is slightly redundant given the required-parameters list, which keeps it from a 5.

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 single-record public read with no output schema and full annotation coverage, the description supplies enough to call it correctly. The only gap is that the return shape is summarized ('links and socials') rather than characterized, which is acceptable for this complexity.

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 all four parameters are already documented, including the '@'-optional handle format. The description's 'Requires `handle`' merely repeats the schema's 'Required.' note and adds no new meaning; 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 uses a specific verb and resource ('Get a public Linktree profile by handle') and states what the result contains ('including links and socials'). The platform name in the tool name already separates it from the many other *_profile_get siblings, but the description itself never routes the agent explicitly.

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?

There is no guidance on when to choose this tool over the sibling profile tools or when it is inapplicable. The only precondition given ('Requires `handle`') is already enforced by the required-parameters list in the schema.

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