Get top search queries for a project from Search Console data. Returns query text, total clicks, impressions, avg CTR, avg position. Use for keyword analysis, content strategy, SEO optimization, finding ranking opportunities.
ConnectorNo auth
650,521 tools. Updated 2026-10-14 00:42
"A search for information about SEO (Search Engine Optimization)" matching MCP tools:
- TESSA's SEO offer in structured form: what it is, starting prices word for word from the pricing page (local, national and international SEO, Generative Engine Optimization), the service page, and the link to book a free strategy session for the scope and an exact price. Scope, deliverables and timeline are included where TESSA has published them. Use this when someone asks about TESSA's SEO, local SEO, national SEO or Generative Engine Optimization (GEO).ConnectorNo auth
- Starts tracking search `terms` for a project and returns `added`, the number of new keywords. Pass terms as an array of plain search phrases (terms: ["seo tool", "rank tracker"]) with the projectId from add_project or list_projects. Terms are lowercased, and one already tracked is skipped, so calling again is safe. Adding measures no rank: call check_rankings for positions. Search volume and difficulty arrive within about ten minutes, looked up in one request pooled with other keywords, costing one keyword_lookups unit per keyword; read them with list_keywords.ConnectorNo auth
- Enable or disable an AI module on a site. The module must be in the plan's available module list. Requires: API key with write scope. Args: slug: Site identifier module_name: Module to toggle. Available modules: "chatbot" (AI chat widget), "seo" (SEO optimization), "translation" (content translation), "content" (AI content generation) Returns: {"module": "chatbot", "enabled": true, "message": "Module enabled"} Errors: NOT_FOUND: Unknown slug or module not in plan VALIDATION_ERROR: Invalid module nameConnectorNo auth
- Amazon keyword / SEO / PPC data for either a single product (ASIN-scope — terms the product ranks for) or a niche/category (keyword-scope — search data around the term). Pass BOTH `asin` and `keyword` to get the product's position for exactly that keyword (e.g. "organic rank of B0... for standing lamp") — the reply gives the exact-match row as the answer and lists look-alike keywords with extra symbols separately; never report a look-alike's rank for the requested keyword. Every keyword row carries search volume, average sales, CPC and trend; ASIN-scope rows ALSO carry this product's own placement for that term — organic rank + page, sponsored page, and relevance score (rows the product does not rank for are marked "not ranking"). Pure data fetch (no AI analysis). How to use: pick high-volume / low-competition terms for SEO and PPC targeting, use CPC as ad-cost pressure, sum search volumes to gauge niche demand, and for ASIN-scope check organic vs sponsored ranks to spot listing-optimization gaps. Marketplace: if the user has not named a country / Amazon domain in this conversation, ask them once which marketplace they work on and reuse that code for every later call in the chat; do not assume the US. Called without `marketplace`, this tool fetches nothing and answers "MARKETPLACE NEEDED". Money is in that marketplace's local currency.ConnectorNo auth
- Suggest the top 10 SEO keywords for a topic with estimated relative search volume and difficulty. Use for early keyword ideation and content planning. Based on model training knowledge, not a live lookup; figures are estimates. Not live keyword-tool data; validate volumes in an SEO tool before committing budget. For a posting schedule, use generate-content-calendar. Pay-per-call: $0.04 USDC on Base via x402. Without a payment-signature header the call returns an error whose data carries the payment terms.ConnectorNo auth
Matching MCP Servers
- FlicenseAqualityDmaintenanceEnables searching documentation from GitHub repositories and web pages via MCP tools, with in-memory indexing and caching for fast retrieval.3-
- AlicenseNot gradedqualityBmaintenanceEnables AI to perform fast, multi-source web searches and research through tools for web, social, news, GitHub, and document analysis.MIT
Matching MCP Connectors
Web search for AI agents. Ranked results with page passages already extracted, plus URL to markdown.
Search PubMed and summarize biomedical literature — designed for AI health agents.
- Brave Local Search API returns enriched information (address, phone, hours, rating) for location-search results. Access requires the Brave Search API Pro plan; currently US-only. Two-step flow: first call `brave_web_search` with `result_filter=locations` to obtain `locations.results[].id`, then pass them here. NOTE: This tool takes location IDs from a prior web-search response; if you have a free-text query, call `brave_web_search` first.ConnectorOAuth
- Get the precomputed result for one scenario of an optimization demo. Returns the verbatim engine output JSON (AMOS for tariff/coffee, SSO output for sso-basic) including the optimal sourcing/production/transport decisions, costs, and any open/close facility variables. ANTI-FABRICATION: every numeric result is verbatim from the optimization engine that ran offline — quote them in your reply, do not round or recompute. Call describe_opt_demo first to learn valid scenario_key formats for each demo.ConnectorNo auth
- List and search keywords with filtering, sorting, and pagination options. PURPOSE: Retrieve a paginated list of keywords from the Metadata platform with advanced sorting and filtering capabilities. Optionally search by keyword name. Use this tool to discover, analyze, and export keyword data for campaign planning and optimization. WHEN TO USE: - Browse all available keywords in the account - Search for specific keywords by name - Find keyword variations and similar terms - Export keyword data with custom sorting - Analyze keyword metrics (search volume, bid prices) - Build keyword lists for campaign creation - Filter keywords by archived status - Compare keyword performance metrics KEY FEATURES: - NAME SEARCH: Filter by keyword name for targeted searches (optional) - PAGINATION: Use page and size parameters to navigate large datasets - SORTING: Sort by creation order (the default, newest first), search volume, bid prices, name, or modification date - FILTERING: Include or exclude archived keywords - PERFORMANCE DATA: Get avgMonthlySearches, lowerPageBid, higherPageBid metrics NAME SEARCH: The optional 'name' parameter supports: 1. Single name (string): Searches for one keyword name - "marketing" → Finds "digital marketing", "email marketing", "marketing automation" - "seo" → Finds "SEO services", "SEO tools", "SEO analytics" - "ppc" → Finds "PPC advertising", "PPC campaigns" 2. Multiple names (array of strings): Searches for multiple keywords at once - ["marketing", "seo", "ppc"] → Aggregates results from all three searches - Makes separate API requests for each name and combines results - Automatically deduplicates keywords by ID - Returns all unique keywords matching any of the provided names - Omit 'name' parameter to list all keywords without filtering - Both single and multiple searches support partial matching PAGINATION STRATEGY: The API returns paginated results. Use these parameters to navigate: - page: 0-based page number (default: 0, meaning first page) - size: Number of results per page (default: 25, recommended: 25-100) To get the next page of results, increment the 'page' parameter. Example: - page=0, size=25 → Returns items 0-24 - page=1, size=25 → Returns items 25-49 - page=2, size=25 → Returns items 50-74 SORT OPTIONS (use format: field,direction): Available fields for sorting: - avgMonthlySearches,desc/asc: Sort by average monthly search volume - lowerPageBid,desc/asc: Sort by lower page bid (CPC floor price) - higherPageBid,desc/asc: Sort by higher page bid (CPC ceiling price) - name,desc/asc: Sort by keyword name alphabetically - id,desc/asc: Sort by creation order, newest first with desc (default) - modifiedDate,desc/asc: Sort by when the keyword was created or last re-saved, archived or unarchived Direction options: - desc: Descending order (highest to lowest) - asc: Ascending order (lowest to highest) SORT EXAMPLES: - sort="avgMonthlySearches,desc": Keywords with highest search volume first - sort="avgMonthlySearches,asc": Keywords with lowest search volume first - sort="lowerPageBid,desc": Keywords with highest CPC floor first - sort="higherPageBid,asc": Keywords with lowest CPC ceiling first - sort="name,asc": Keywords in alphabetical order (A-Z) - sort="name,desc": Keywords in reverse alphabetical order (Z-A) FILTERING: - archived: Filter by archived status (true/false, default: false) Set to true to include archived keywords Set to false to show only active keywords (recommended) PAGINATION WORKFLOW: 1. Start with page=0 to get the first set of keywords 2. Check the response metadata to see if more results exist 3. If needed, increment page number and fetch again 4. Continue until all desired results are retrieved PARTIAL PAGES: A page is partial when totalElements is larger than the rows it returns, and the response then carries a `note` saying so. A multi-name search counts only the rows it read, so its `note` names the searches that had more matches than one page or that failed. A keyword missing from a partial result may still exist: search it by name, or read the other pages, before saying it does not exist. To confirm keywords you just created, search them by name: a name that already existed keeps its old id, so it is not among the newest rows. RESPONSE FORMAT: Returns a paginated response with: { "totalElements": 2, "totalPages": 1, "data": [ { "name": "product match", "avgMonthlySearches": 260, "competition": "LOW", "lowerPageBid": 0.00, "higherPageBid": 0.00, "id": 18330, "archived": false, "createdDate": "2025-09-15T20:35:50.000Z", "modifiedDate": "2025-09-30T21:14:59.000Z" }, { "name": "keyword match", "avgMonthlySearches": 140, "competition": "LOW", "lowerPageBid": 0.00, "higherPageBid": 0.00, "id": 18339, "archived": false, "createdDate": "2025-09-15T20:35:50.000Z", "modifiedDate": "2025-09-30T21:14:59.000Z" } ] } A partial result also carries a top-level `note` string (see PARTIAL PAGES). COMMON USE CASES: 1. List all active keywords: list_keywords() 2. Search for "marketing" keywords: list_keywords(name="marketing") 3. Get top 50 keywords by search volume: list_keywords(page=0, size=50, sort="avgMonthlySearches,desc") 4. Find expensive keywords (highest CPC) with name search: list_keywords(name="analytics", sort="higherPageBid,desc") 5. Find affordable keywords (lowest CPC): list_keywords(sort="lowerPageBid,asc") 6. Get alphabetically sorted active keywords: list_keywords(page=0, size=100, sort="name,asc", archived=false) 7. Export all keywords (paginate through results): list_keywords(page=0, size=100) list_keywords(page=1, size=100) list_keywords(page=2, size=100) ... (repeat for all pages shown in totalPages) 8. Get the newest keywords (the default order): list_keywords(page=0, size=25) Get recently created or changed keywords: list_keywords(page=0, size=25, sort="modifiedDate,desc") 9. Search with pagination: list_keywords(name="marketing", page=0, size=50) list_keywords(name="marketing", page=1, size=50) 10. Search for multiple keyword names at once: list_keywords(name=["marketing", "seo", "ppc"]) 11. Search multiple names with sorting: list_keywords(name=["analytics", "ads"], sort="avgMonthlySearches,desc") 12. Search multiple names and exclude archived: list_keywords(name=["social", "media"], archived=false) PARAMETERS: - name: Optional keyword name or partial name to search for. Can be a string or array of strings. Supports partial matching. Omit to list all keywords. (optional) - archived: Filter by archived status (default: false) - page: Page number for pagination (0-based, default: 0) - size: Number of items per page (default: 25, max recommended: 100) - sort: Sort criteria in format: field,direction (default: id,desc, newest first) PERFORMANCE TIPS: - Use size=100 for bulk exports to reduce API calls - Use page number to efficiently navigate large datasets - Filter by archived=false to exclude inactive keywords - Keep the default id,desc to see recently created keywords first - Sort by modifiedDate,desc to see recently created or changed keywords - Use name parameter for targeted searches to reduce result set - When searching multiple names, each name triggers a separate API call Use reasonable list sizes to avoid excessive API calls EXAMPLES: - list_keywords() - Get first 25 active keywords - list_keywords(name="marketing") - Search for marketing keywords - list_keywords(name=["marketing", "seo"]) - Search multiple keywords - list_keywords(page=0, size=50, sort="avgMonthlySearches,desc") - Top 50 by search volume - list_keywords(name="seo", sort="avgMonthlySearches,desc") - SEO keywords by search volume - list_keywords(name=["ads", "analytics"], sort="higherPageBid,desc") - Multiple names by bid price - list_keywords(page=1, size=100, archived=false, sort="name,asc") - Page 2 of keywords A-Z - list_keywords(page=0, size=25, sort="lowerPageBid,desc") - Most expensive keywordsConnectorAPI key
- Search the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search through Linkedin profiles / companies respectively. If highlights are insufficient, follow up with web_fetch_exa on the best URLs.ConnectorNo auth
- General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find the address behind a Nansen label (public figure, fund, exchange wallet) - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)ConnectorNo auth
- General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find the address behind a Nansen label (public figure, fund, exchange wallet) - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)ConnectorNo auth
- Reference text on supply-chain network optimization — mixed-integer programming (MIP), the structure of decision variables and constraints, the objective function for landed-cost minimization, and the common problem classes (facility selection, sourcing, flow constraints, multi-period, BOM/production, multi-objective). Also covers when to reach for optimization vs simulation. Pure static text — no engine call, deterministic output. Use this when the user asks a conceptual 'how does network optimization work' question. ChiAha's AMOS optimizer (open-source, Odin, GLOP/CBC via OR-Tools) powers the Tariff and Coffee Co-pack demos on the sandbox.ConnectorNo auth
- Search Pick an Agency's directory of 47,000+ marketing agencies. Filter by free-text query, service (e.g. SEO, paid ads, social media), country, city, industry, and minimum rating. Returns the top matches with location, rating, reviews and profile link. WHEN TO USE: for browsing or filtering ('show me SEO agencies in Berlin', 'agencies named X') when the user wants a LIST to explore. Use match_agencies instead when the user describes their project/brief and wants a RECOMMENDATION; use get_agency for full detail on one specific agency.ConnectorNo auth
- Get comprehensive usage guide for FundingLandscape tools. Call this FIRST to understand optimal workflows, parameter usage, and best practices. Returns detailed documentation for search tools, filters, and token optimization strategies. Does not count toward your monthly searches.ConnectorNo auth
- Audits content for Answer Engine Optimization (AEO): Evaluates concise 40-60 word direct answer definition blocks, question-based H2/H3 subheadings (What/How/Why), FAQ schema alignment, and citation readiness for Google AI Overviews and Perplexity. USAGE GUIDELINES: - Use when optimizing content to win conversational AI search citations, direct answers, and Perplexity summaries. - Do NOT use for brand knowledge-graph entity reconciliation; use 'seo_audit_geo' instead. - Do NOT use for standard on-page metadata; use 'seo_audit_onpage' instead. BEHAVIORAL TRANSPARENCY: - Safe, read-only diagnostic evaluation. No file modifications.ConnectorNo auth
- Audits Generative Engine Optimization (GEO): Evaluates brand and organization entities, Schema.org Organization/Person definitions, sameAs knowledge graph reconciliation (Wikidata, LinkedIn, Crunchbase), and Author E-E-A-T credentials. USAGE GUIDELINES: - Use to evaluate how LLM-based search engines (ChatGPT Search, Claude, Gemini) comprehend brand identity and authority. - Do NOT use for local map pack NAP consistency; use 'seo_audit_local' instead. - Do NOT use for direct answer snippet definitions; use 'seo_audit_aeo' instead. BEHAVIORAL TRANSPARENCY: - Safe, read-only diagnostic evaluation. No file modifications.ConnectorNo auth
- Tests a live website or local endpoint for Web MCP enablement: Checks Streamable HTTP (/mcp), Legacy SSE (/sse), discovery manifests (/.well-known/mcp/server-card.json, llms.txt), CORS headers, and provides copy-paste implementation blueprints in 11 programming languages. USAGE GUIDELINES: - Use to test if a web application exposes an agent-accessible Model Context Protocol interface. - Do NOT use for regular HTML search engine optimization; use 'seo_audit_technical' or 'seo_audit_onpage' instead. BEHAVIORAL TRANSPARENCY: - Safe, read-only protocol diagnostic probe. Makes HTTP GET/HEAD requests to standard discovery endpoints. Modifies no files.ConnectorNo auth
- Execute live web searches using multi-engine chain (TinyFish, DuckDuckGo, Jina) without monthly API subscriptions. Returns fresh source URLs, titles, and snippets. Requires x402 micropayment (0.005 USDC on Base). When to use: Real-time web browsing and information retrieval for AI agents. When NOT to use: Do NOT use for deep recursive crawling of entire sites. Parameters: - `query` (string, required): Search query (3-300 chars). - `limit` (integer, optional, default 5): Maximum number of search results to return (1-10).ConnectorNo auth
- Universal search tool supporting all SerpApi engines and result types. When to use: - Any query needing live, structured SERP data: web results, news, product listings, job postings, local businesses, flight/hotel prices, video results, images, stock/weather cards, knowledge graph entities. Engine discovery via MCP resources: - serpapi://engines lists all engines supported by this tool. - serpapi://engines/<engine> provides engine-specific parameters and supported options. - Example: serpapi://engines/google_news Input schema: params: JSON object containing SerpApi engine parameters. Common parameters: - q: Search query. Required for most engines. - engine: SerpApi engine name. Defaults to "google_light". - location: Optional geographic location for localized results. - output: Optional response format. Omit for JSON (default), or set to "md" for Markdown. Engine-specific parameters are available via MCP resources: - serpapi://engines lists all supported engines. - serpapi://engines/<engine> provides parameters and options for one engine. mode: Response mode. Defaults to "complete". - "complete": Return the full SerpApi response. - "compact": Remove metadata fields from JSON responses. Markdown is returned unchanged. Output schema: structuredContent.result contains the response string: serialized JSON or unchanged Markdown. The same string is included in text content. Tool failures preserve this wrapper and set isError to true. Guided search: Searches can request missing engine parameters from supporting clients using the engine catalog and engine-specific rules. Flights collect airports and dates, hotels collect the destination and stay dates, and directions collect missing endpoints. Other clients receive a missing-parameter error. Cancellation does not run a search. Examples: Weather: {"params": {"q": "weather in London", "engine": "google"}, "mode": "complete"} Stock: {"params": {"q": "AAPL stock", "engine": "google"}, "mode": "complete"} General: {"params": {"q": "coffee shops", "engine": "google_light", "location": "Austin, TX"}, "mode": "complete"} Compact: {"params": {"q": "news"}, "mode": "compact"} Markdown: {"params": {"q": "news", "output": "md"}} Supported engines include (not limited to): - google - google_light - google_flights - google_hotels - google_images - google_news - google_local - google_shopping - google_jobs - bing - yahoo - duckduckgo - youtube_search - baidu - ebayConnectorNo auth
- Execute live web searches using multi-engine chain (TinyFish, DuckDuckGo, Jina) without monthly API subscriptions. Returns fresh source URLs, titles, and snippets. Requires x402 micropayment (0.005 USDC on Base). When to use: Real-time web browsing and information retrieval for AI agents. When NOT to use: Do NOT use for deep recursive crawling of entire sites. Parameters: - `query` (string, required): Search query (3-300 chars). - `limit` (integer, optional, default 5): Maximum number of search results to return (1-10).ConnectorNo auth