read_webpage
Fetch and extract text content from a webpage
LABSCO SUMMARY
Finding a source and reading it are one hop apart, so a claim gets checked instead of repeated.
The two tools close the loop between a query and the actual page, which means an answer can cite the text it came from rather than a search snippet. num is the only lever on how much of the context window a research pass costs, and the scope of what is searchable is set once in the programmable search engine rather than per query.
What it is
Two tools that cover a research loop: search runs a web query through your own Google programmable search engine and returns results, and read_webpage fetches a URL and extracts its text content.
What you get
- A web search returning results, with num controlling how many come back
- The text content of any page, extracted from a URL you pass
- A search engine whose scope is yours: results reflect however the programmable search engine in GOOGLE_SEARCH_ENGINE_ID is configured
Requirements
A Google API key in GOOGLE_API_KEY and a programmable search engine ID in GOOGLE_SEARCH_ENGINE_ID, plus Node on your PATH.
Setup effort
One command plus a key — npx -y @adenot/mcp-google-search, then supply credentials
USE CASES
01
Checking a claim against the page it came from
Search for the claim, then fetch the most promising result and read its text — so what gets quoted is the source rather than a search snippet.
02
Reading a page you already have the link to
Skip the search entirely when a URL turns up in a ticket or a message and what you need is the content behind it.
03
Keeping a research pass inside a context budget
num decides how many results come back, which is the one lever on how much of the window a broad query consumes before you have read anything.
2 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
search
Perform a web search query
BEFORE YOU INSTALL
What to know first
Tools you get
2 tools when we connected.
Requires
- npx on PATH
- GOOGLE_API_KEY in your environment
- GOOGLE_SEARCH_ENGINE_ID in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @adenot/mcp-google-searchMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"google-search": {
"command": "npx",
"args": [
"-y",
"@adenot/mcp-google-search"
],
"env": {
"GOOGLE_API_KEY": "<YOUR_GOOGLE_API_KEY>",
"GOOGLE_SEARCH_ENGINE_ID": "<YOUR_GOOGLE_SEARCH_ENGINE_ID>"
}
}
}
}
