| name | linkup |
| description | Web search and content fetching using Linkup extension. Use when needing to search the web, get answers to questions with sources, or fetch content from specific URLs. Provides three tools: linkup_web_search (discovery), linkup_web_answer (direct answers), linkup_web_fetch (URL content extraction). |
Linkup Extension
Web search and content fetching tools powered by Linkup API.
Tools
linkup_web_search
Search the web and get sources with content snippets.
linkup_web_search(query: string, depth?: "fast" | "standard" | "deep", limit?: number)
query: Be specific and detailed. Include context like dates, locations, company names.
depth: Search depth mode. Default: "standard".
fast: Sub-second latency, uses pre-indexed "atoms of information". Best for quick facts and simple lookups.
standard: Single iteration retrieval. Balanced speed and depth for most queries.
deep: Up to 10 iterations with chain-of-thought reasoning. Best for complex multi-step research (slower).
limit: Maximum number of results. Default: 10.
Search result content is truncated per result. If a result is truncated, the tool output includes a temp file path with the full result content.
Use when: Discovering information across multiple sources, researching topics, comparing perspectives.
linkup_web_answer
Get a synthesized answer with source citations.
linkup_web_answer(query: string, depth?: "fast" | "standard" | "deep")
query: Be specific and detailed.
depth: Same depth modes as linkup_web_search. Default: "standard".
The answer and source snippets are truncated independently. If any block is truncated, the tool output includes a temp file path with the full block content.
Use when: Need a direct answer to a specific question, quick facts with citations.
linkup_web_fetch
Fetch content from a URL as clean markdown.
linkup_web_fetch(url: string, renderJs?: boolean)
url: The URL to fetch.
renderJs: Set false for static pages (faster). Default: true.
Fetched markdown is truncated when large. If it is truncated, the tool output includes a temp file path with the full markdown content.
Use when: Reading documentation, following up on search results, extracting content from known URLs.
Tool Selection
| Need | Tool |
|---|
| Find information across sources | linkup_web_search |
| Get a direct answer with sources | linkup_web_answer |
| Read content from a known URL | linkup_web_fetch |
Query Formulation
Good queries are specific:
| Bad | Good |
|---|
| "Microsoft revenue" | "Microsoft fiscal year 2024 total revenue" |
| "React hooks" | "React useEffect cleanup function best practices" |
| "AI news" | "OpenAI announcements January 2026" |
Add context:
- Time: "2025", "last quarter", "since version 5.0"
- Location: "French company Total", "US market"
- Specifics: company names, version numbers, exact terms
Depth Mode Selection
Fast: Sub-second responses for quick facts, simple lookups, known facts.
Standard (default): Single iteration, balanced speed/depth for most queries.
Deep: Complex research, multi-step queries, comprehensive coverage needed.
// Fast - instant facts, sub-second
linkup_web_search("Node.js 22 release date", depth: "fast")
// Standard - balanced, one search iteration
linkup_web_search("React useEffect cleanup best practices")
// Deep - complex research, multiple iterations
linkup_web_search("comparison of Rust web frameworks performance benchmarks 2025", depth: "deep")
Common Patterns
Research workflow
linkup_web_search to discover sources
linkup_web_fetch on promising URLs for full content
Quick facts
linkup_web_answer for direct answer with citations
Documentation reading
linkup_web_fetch on known documentation URL
Commands
/linkup:balance - Check remaining API credits