BuzzSearch MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BUZZSEARCH_API_KEY | Yes | Your BuzzSearch API key | |
| BUZZSEARCH_MCP_URL | No | Override the server URL | https://buzzsearch.ai/api/mcp |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Research what real people say about a product, problem or audience across Reddit, YouTube, TikTok and Facebook groups. Runs a full search: discovers threads and videos, reads their comments, extracts verbatim quotes and writes a cited answer. A query that contains a TikTok video, creator or hashtag link, a YouTube video link, a Reddit thread or subreddit link, or a Facebook group post link reads that link's own comments directly (add a question after the link to also search the topic). Waits up to |
| get_searchA | Read a search's status, cited answer, coverage counts and top quotes. Free. Pass |
| get_quotesA | Verbatim customer quotes extracted by a search, filtered and paged. Free. Each quote carries a stable id, the source url, a dimension (emotional_painpoints, recurring_painpoints, desired_outcomes, failed_solutions, objections, customer_lingo), an engagement score and an emotional intensity (1 to 5). For ad copy, pull emotional_painpoints and customer_lingo sorted by intensity. |
| get_sourcesA | The threads and videos a search read, with engagement, comment counts and how many quotes each produced. Free. Use it to cite a thread or pick which source's raw comments to pull. |
| get_commentsA | The raw comment bodies behind a completed search, grouped by thread or video, filtered and paged. Free. A search reads hundreds to thousands of comments, so filter by source, a substring, or a minimum score, and page with limit and offset. |
| askA | Ask a new question over a completed search's corpus and get a cited answer, without searching again. Much cheaper than a new search: only the answer is metered at the API rate. Good for 'what do they say about price', 'summarize the objections', 'which phrases do they use for the problem'. Works on searches started through the API or MCP. |
| generate_hooksA | Write ad hooks grounded in a completed search's quotes, using BuzzSearch's hook writer: each hook opens with a callout lifted from real comments and carries a loop or promise. Metered at the API rate, no new search. Give an |
| list_searchesA | Recent searches by the signed-in user, newest first, including ones run in the BuzzSearch app. Free. Reread a past search with get_search or get_quotes instead of paying for a new one on the same topic. |
| get_balanceB | The user's BuzzSearch credit balance. Searches draw from it at the API rate; top up at buzzsearch.ai. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| research | Run a BuzzSearch search and summarize the pains, desires and objections with cited quotes. |
| ad-script | Turn a completed BuzzSearch search into ad scripts grounded in real customer language. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Tools target distinct resources (search vs sources vs quotes vs comments vs hooks vs balance), but 'search' and 'ask' both produce cited answers and could be confused despite the cost/staleness distinction. 'get_search' and 'get_sources' also have somewhat overlapping retrieval roles, though descriptions clarify the boundaries.
All names are lowercase snake_case verb_noun: get_sources, get_search, get_quotes, get_comments, get_balance, list_searches, generate_hooks, ask, search. The single-word 'search' and 'ask' are idiomatic and consistent with the imperative pattern.
Nine tools is well-scoped for a research/search server: one expensive action, several free readers, and two generators. Each tool earns its place without obvious redundancy.
The lifecycle covers search, status, follow-up (ask), source/quote/comment retrieval, hook generation, history and balance. Minor gaps: no delete/cancel search, no export, and no explicit tool to fetch a single source by id beyond list-level get_sources, but core workflows are complete.