Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

linktree

Fetches a public link-in-bio page and returns its profile links and metadata through the Fetchproof API.

Instructions

linktree: Linktree page. GET /v1/linktree. Linktree page Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "url": "<url>"
    },
    "name": "linktree"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL to Linktree page
cache_max_ageNoUse a cached response this old or newer for 0 credits. If none is available, fetch live at the endpoint’s normal price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose a non-obvious behavioral trait: the credit cost model, including that failures, blocked/timed-out requests, and cache hits are free. It still says nothing about what the response contains, whether the page is scraped live or proxied, or any rate limiting beyond the cache parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the resource but wastes a sentence repeating 'Linktree page' and the route a second time. The pricing paragraph is long and reads like boilerplate shared across the catalog rather than information specific to this tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-URL fetch with no output schema, the description covers cost semantics but leaves the return shape entirely unstated, so an agent cannot anticipate whether it gets bio, links, or raw HTML. Adequate but with a clear gap.

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 both url and cache_max_age are already documented including an example. The description adds no further syntax or format detail about the URL, 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?

States the resource ('Linktree page') and implies retrieval via the route GET /v1/linktree, so an agent knows it fetches a Linktree profile page. It does not distinguish itself from siblings like facebook_profile or bluesky_profile, which would need a sentence about platform-specific coverage.

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?

No when-to-use or when-not-to-use guidance is given beyond the implied 'you have a linktr.ee URL'. There is no mention of alternatives or of conditions under which another tool should be preferred.

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