Skip to main content
Glama
VincentKaufmann

noapi-google-search-mcp

by VincentKaufmann
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

subscribe

Subscribe to content sources such as news, Reddit, GitHub, or YouTube for automatic monitoring. After subscribing, fetch and search feeds to retrieve relevant information.

Instructions

Subscribe to a content source for automatic monitoring and search.

Supported source types: news, reddit, hackernews, github, arxiv, youtube, podcast, twitter.

After subscribing, run check_feeds to fetch content, then search_feeds to query it.

Sample prompts that trigger this tool: - "Subscribe to BBC News" - "Follow r/LocalLLaMA on Reddit" - "Monitor Hacker News top stories" - "Watch anthropics/claude-code on GitHub for new releases" - "Subscribe to the YouTube channel @3Blue1Brown" - "Follow @elonmusk on Twitter" - "Subscribe to the machine learning arXiv category" - "Add this podcast: https://feeds.example.com/podcast.xml" - "Subscribe to CNN, NPR, and The Guardian"

Args: source_type: One of: news, reddit, hackernews, github, arxiv, youtube, podcast, twitter. identifier: Source identifier — depends on type: - news: preset name (bbc, cnn, nyt, guardian, npr, aljazeera, techcrunch, ars, verge, wired, reuters) or a custom RSS URL - reddit: subreddit name (e.g. "LocalLLaMA", "programming") - hackernews: "top", "new", or "best" - github: "owner/repo" (e.g. "anthropics/claude-code") - arxiv: shortcut (ai, ml, cv, nlp, robotics, crypto) or arXiv category like "cs.AI" - youtube: channel handle (@name), URL, or channel ID (UCxxxx) - podcast: RSS feed URL - twitter: username with or without @ (e.g. "elonmusk") name: Optional display name for this subscription.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_typeYes
identifierYes
nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.3/5.0
Behavior3/5

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

No annotations provided, so description carries burden. It explains the subscription action and workflow but does not disclose idempotency, rate limits, or error handling.

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

Conciseness4/5

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

Well-structured with purpose first, then details. Slightly verbose with many examples, but each section earns its place.

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

Completeness5/5

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

Covers all necessary aspects: what, when, how, parameters, and ties to sibling tools. Output schema existence reduces need for return value details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage, but description gives exhaustive per-type identifier formats and allowed values for source_type, fully compensating.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool subscribes to a content source for monitoring and search, listing specific types. It distinguishes from siblings like check_feeds and unsubscribe.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit workflow (subscribe then check_feeds, search_feeds) and sample prompts. Lacks explicit when-not-to-use but context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/VincentKaufmann/noapi-google-search-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server