glim.sh

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Give your agent live data from Twitter, Reddit, the web and GitHub. No API keys, no scraping stack.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "glim.sh": {
      "url": "https://glim.sh/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (14)

• glim_twitter_search read-only

  Search Twitter/X. Returns a compact human-readable list by default; pass format='json' for full structured data. Use glim_twitter_get(ref) for full thread context. Use docs://search-operators for reference.

  Parameters:

  • query (required) — string — Search query with operators (e.g. 'from:elonmusk AI min_faves:100 within_time:7d')
  • sort — string — Sort by relevance or recency: "top" (most engaged tweets matching the query - best for "what's the conversation about X") or "latest" (newest first - best for monitoring/recency). Default: "top".
  • cursor — string — Pagination cursor from previous search. Ranking is strongest on page 1 - paged results under sort:'top' trend toward recency (upstream behavior).
  • format — string — Output format. 'text' (default): compact human-readable view, fewer tokens. 'json': full structured data for machine parsing.
  • end_date — string — Only tweets before this time. YYYY-MM-DD (inclusive through end of day UTC) or ISO 8601 datetime with Z/offset (e.g. 2026-04-13T14:30:00Z)
  • start_date — string — Only tweets on or after this time. YYYY-MM-DD (UTC midnight) or ISO 8601 datetime with Z/offset (e.g. 2026-04-13T14:30:00Z)
  • expand_urls — boolean — When true, auto-crawl entity URLs and attach crawled_content to tweets. Off by default: responses can grow by up to 4KB per expanded URL. Use glim_web_fetch(url) for targeted crawls instead.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• glim_twitter_get read-only

  Fetch a tweet or a user from one reference. A tweet URL (incl. handle-less /i/status/<id>) returns the tweet with full thread context, parent, and optional replies/quotes; a profile URL (https://x.com/<handle>) returns the user with recent tweets. Prefer full URLs - if you only have a numeric id, pass it as a quoted string. Returns a compact human-readable view by default; pass format='json' for full structured data.

  Parameters:

  • ref (required) — string — Tweet URL or profile URL. A tweet URL (incl. /i/status/<id>) returns the tweet + thread; a profile URL (https://x.com/<handle>) returns the user + recent tweets. Prefer full URLs - if you only have a numeric id, pass it as a quoted string.
  • cursor — string — Profile refs only: pagination cursor from next_cursor
  • format — string — Output format. 'text' (default): compact human-readable view, fewer tokens. 'json': full structured data for machine parsing.
  • include — array — Tweet refs only: also fetch 'replies' and/or 'quotes'
  • expand_urls — boolean — When true, auto-crawl entity URLs and attach crawled_content to tweets. Off by default: responses can grow by up to 4KB per expanded URL. Use glim_web_fetch(url) for targeted crawls instead.
  • include_replies — boolean — Profile refs only: include replies in the timeline
  • include_mentions — boolean — Profile refs only: include the mentions timeline

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• glim_reddit_search read-only

  Search Reddit posts. Each result comes with full post content and its top comments, so a single search usually answers the question without follow-up. Compact human-readable text by default; pass format='json' for full structured data. Use glim_reddit_get(ref) for a single post's complete comment tree. Page with cursor (response gives next_cursor when more exist). See docs://reddit-search.

  Parameters:

  • query (required) — string — Search query (e.g. 'subreddit:programming machine learning')
  • sort — string — Sort order. Keep 'relevance' (default) for question or topic queries - it ranks by how well posts match your query. 'top'/'hot' rank by score/recency and largely ignore the query text, so use them only to browse what's popular in a subreddit.
  • time — string — Time range
  • limit — integer — Max posts (1-10), each with full content + top comments
  • cursor — string — Pagination cursor from a prior response's next_cursor
  • format — string — Output format. 'text' (default): compact human-readable view, fewer tokens. 'json': full structured data for machine parsing.
  • end_date — string — Only posts before this date (YYYY-MM-DD)
  • start_date — string — Only posts on or after this date (YYYY-MM-DD)

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• glim_reddit_get read-only

  Fetch a Reddit post, subreddit, or user by ref. Posts return comments; subreddits and users return profile metadata plus recent activity.

  Parameters:

  • ref (required) — string — Post ID or URL, subreddit ref (r/programming or reddit.com/r/programming), or user ref (u/spez or reddit.com/user/spez)
  • sort — string — Listing post sort
  • time — string — Listing time range
  • limit — integer — Max subreddit posts (1-10), each with full content + top comments
  • cursor — string — Pagination cursor from a prior subreddit response's next_cursor
  • format — string — Output format. 'text' (default): compact human-readable view, fewer tokens. 'json': full structured data for machine parsing.
  • comment_sort — string — Comment sort. Post refs only: subreddit/user listings always hydrate a fixed 2 top-level comments sorted by top.
  • comment_depth — integer — Max nesting depth (post refs only)
  • comment_limit — integer — Max comments (post refs only)
  • include_posts — boolean — Include recent posts for user refs
  • include_comments — boolean — Include recent comments for user refs

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• glim_web_search read-only

  Semantic web search powered by Exa. Returns titles, URLs, and the top query-relevant excerpt per result. Compact text by default; pass format='json' for full structured data incl. all excerpts per result. Use glim_web_fetch(url) for full page content. Matching is semantic, so a query with no real match still returns ten nearest-neighbour results rather than zero - judge relevance from the excerpts, not from the result count.

  Parameters:

  • query (required) — string — Search query
  • format — string — Output format. 'text' (default): compact human-readable list, fewer tokens. 'json': the same results as structured data (title, url, snippet, score, published_date, author).
  • exclude_domains — array — Exclude results from these domains. Useful for filtering noisy aggregators or SEO farms when you've seen them dominate results (e.g. ['pinterest.com', 'quora.com']).
  • include_domains — array — Restrict results to these domains (e.g. ['arxiv.org'])
  • published_within_days — integer — Restrict to results published within the last N days. Skip this for broad queries - it excludes pages without publish-date metadata. Common values: 1, 7, 30, 365.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• glim_web_fetch read-only

  Fetch a single web page and extract clean content. Auto-tier server-side: handles SSR (Next.js, Nuxt, TikTok, Pinterest, YouTube), SPA shells, PDFs, paywall detection, residential-proxy escalation, and stealth profiles for TikTok / Instagram / Pinterest / YouTube. Returns clean markdown (default) with a YAML frontmatter header (url, outcome, total_chars). Read 'outcome' to classify the result (success | teaser | thin_content | paywall | bot_challenge | consent_wall | login_wall | rate_limited | timeout | transient_upstream | unsupported_target | not_found | error). Large pages (>80k chars) are truncated inline with truncated_chars + a download_full_url to the complete extraction (expires ~1h). Permanently unsupported (outcome=unsupported_target, cost=0 upstream): Bluesky search, Instagram post/reel and tag/explore pages (profiles work), Pinterest search, g2.com, Truth Social, Xiaohongshu. Threads and Instagram profile pages ARE supported.

  Parameters:

  • url (required) — string — URL to fetch
  • format — string — Output format. 'markdown' (default) clean article text; 'html' raw cleaned HTML; 'json' the structured SSR blob (TikTok / Pinterest / YouTube) instead of article text.
  • selector — string — CSS selector to scope the result. An anchor-id selector (e.g. a docs anchor like '#usage') that lands on a heading expands to its whole section; other selectors return the matched elements themselves.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• glim_github_search read-only

  Search GitHub repositories, conversations (issues+PRs), discussions, or code, with full GitHub search syntax in the query: qualifiers (repo:, org:/user:, language:, path:, symbol:, content:, is:, stars:, label:, sort:stars), boolean AND/OR/NOT with parentheses, "exact strings", and /regex/. kind='repos': MINIMAL distinctive keywords - the project/library name only ('rtk', 'react query'); every extra word must ALL match and buries the canonical repo - filter with qualifiers, not prose. kind='code': ONE literal code pattern as it appears in files ('useState('), an "exact string", a /regex/, or symbol:name to find definitions, across 2.8M+ public repos; narrow with repo:/language:/path:. Without repo:/org: a rare literal scans every repo and can end as an incomplete zero - add repo:/org:/language: before retrying it, never resend it unchanged. Not supported in code search: license:, enterprise:, is:vendored, is:generated. kind='conversations': returns compact previews - use glim_github_get for full content; sort: REPLACES relevance ranking (words match anywhere incl. comments), omit it for best matches. kind='discussions': GitHub Discussions, a SEPARATE index from issues/PRs - a question answered there never appears under conversations, so reach for it when a repo does its Q&A in Discussions; supports repo:/org:/author:/is:answered plus category: (the repo's own category name, needs a repo: scope), up to 10 results per page, no sort:. Set repo='owner/name' to scope to one repository (works with any kind; with repos it routes to conversations). kind is optional - inferred from the query (is:answered/category: -> discussions, is:/label: -> conversations, path:/symbol://regex/ -> code, stars:/topic: -> repos, else repos); a conversations search with no matches is retried as discussions and says so. Returns compact text by default; pass format='json' for full structured data.

  Parameters:

  • query (required) — string — Search query in full GitHub search syntax: qualifiers (repo:owner/name, org:/user:, language:, path: with globs, symbol:, content:, is:, stars:>N, label:, sort:stars), boolean AND/OR/NOT with parentheses, "exact strings", and /regex/. kind=repos: minimal distinctive keywords - the project/library name (GOOD: 'rtk', 'react query'; BAD: 'rtk rust token killer' - every extra word must ALL match and buries the real repo; filter with qualifiers, not prose). kind=code: ONE literal code pattern as it appears in files ('useState('), an "exact string", a /regex/, or symbol:name for definitions; narrow with repo:/language:/path:, not extra words. Without repo:/org: a rare literal scans every public repo and can end as an incomplete zero - add repo:/org:/language: before retrying it, since the same unscoped query returns the same result. kind=conversations: keywords plus filters (is:issue, label:bug). kind=discussions: keywords plus repo:/org:/author:/is:answered/category: - a separate GitHub index from issues/PRs, so a thread that lives in Discussions is invisible to kind=conversations (and vice versa). category: matches the repo's own category name (Ideas, Q&A) and needs a repo: scope; sort: does not apply. Caution: sort: REPLACES relevance ranking (sort:reactions = most-popular thread mentioning the words anywhere, incl. comments) - omit sort: for best-match. Not supported in code search: license:, enterprise:, is:vendored, is:generated.
  • kind — string — What to search: 'repos', 'conversations' (issues+PRs), 'discussions' (GitHub Discussions - a separate index from issues/PRs), or 'code' (literal/regex/symbol search across 2.8M+ public GitHub repos). Optional - inferred from the query: is:answered/category: implies discussions, is:/label:/author: implies conversations, path:/symbol:/content://regex/ implies code, stars:/topic:/in:readme implies repos, otherwise repos. type:code / type:repos / type:discussions in the query also works. A conversations search that matches nothing is retried as discussions, so an answer that lives in Discussions is not silently missed.
  • page — integer — Page number
  • repo — string — Scope to one repository. Accepts 'owner/name', a github.com URL, or a partial 'owner/' (code). Works with any kind; setting it with kind=repos routes the search to conversations, since repo-name search can't scope to one repo. Equivalent to a repo: qualifier in the query (if both are given they must match).
  • format — string — Output format. 'text' (default): compact human-readable previews, fewer tokens. 'json': full structured data for machine parsing.
  • per_page — integer — Results per page

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• glim_github_get read-only

  Fetch GitHub data from a single ref. GitHub URL or 'owner/repo' shorthand. A repo URL or owner/repo returns metadata + README; /pull/N -> PR (with comments + changed files), /issues/N -> issue, /discussions/N -> discussion (with threaded replies), /blob/<ref>/<path> -> file (raw.githubusercontent.com URLs work too), /tree/<ref>[/<path>] -> file tree (optionally scoped to a subdirectory), /commit/<sha> -> one commit with diff, /commits[/<ref>/<path>] -> history (optionally for one file), /branches, /releases (or /releases/tag/<tag> | /releases/latest -> one release), /topics/<name> -> top repos with that topic (by stars).

  Parameters:

  • ref (required) — string — GitHub URL or 'owner/repo' shorthand. A repo URL or owner/repo returns metadata + README; /pull/N -> PR (with comments + changed files), /issues/N -> issue, /discussions/N -> discussion (with threaded replies), /blob/<ref>/<path> -> file (raw.githubusercontent.com URLs work too), /tree/<ref>[/<path>] -> file tree (optionally scoped to a subdirectory), /commit/<sha> -> one commit with diff, /commits[/<ref>/<path>] -> history (optionally for one file), /branches, /releases (or /releases/tag/<tag> | /releases/latest -> one release), /topics/<name> -> top repos with that topic (by stars).
  • page — integer — Page number
  • format — string — Output encoding. 'text' (default): compact human-readable text, fewer tokens (file returns raw content). 'json': machine-readable JSON.
  • per_page — integer — Results per page

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• glim_amazon_search read-only

  Pass exactly ONE of {query} or {category_slug}. Searches Amazon (com|co.uk|de|fr|es|it) and returns ranked hits with buybox price (gross + VAT-excluded net), ratings, review counts, and ASINs. Drill down with glim_amazon_get(ref). Set sort_by='most_reviewed' (with min_reviews to filter junk) for a trust-weighted re-rank within the current page. Compact text by default; pass format='json' for full structured data.

  Parameters:

  • tld — string — Amazon marketplace: com | co.uk | de | fr | es | it
  • page — integer — Page number (1-20)
  • query — string — Free-text keyword query (mutually exclusive with category_slug)
  • format — string — Output format. 'text' (default): compact human-readable view, fewer tokens. 'json': the same hits as machine-readable JSON. Text already carries every field except `image_url`, which only json returns.
  • sort_by — string — Server-side sort, except 'most_reviewed' which re-ranks the current page client-side by review count desc (rating tiebreaker). Pair 'most_reviewed' with min_reviews to skip thinly-reviewed items.
  • min_reviews — integer — Drop hits with fewer than N reviews. Pair with sort_by='most_reviewed' for a trust-weighted result. Applied client-side to organic/paid/suggested.
  • include_paid — boolean — Include sponsored ad results (default: dropped)
  • category_slug — string — Amazon bestsellers category slug, e.g. 'electronics' (.com), 'elektronik' (.de), 'electronique' (.fr). Invalid slugs return 'not_found' - retry with a correct slug.
  • include_suggested — boolean — Include 'people also searched for' suggestions (default: dropped)

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• glim_amazon_get read-only

  Fetch Amazon product detail from a full product URL (the marketplace - com|co.uk|de|fr|es|it - is read from the URL host; pass the url field from a glim_amazon_search result, or any /dp/<ASIN> page URL). Returns title, buybox price (gross + VAT-excluded net), stock, delivery estimate, rating, top reviews, and an 'other sellers' summary (count + floor price). Text mode (default) returns a compact view with offers_summary {buybox, lowest_new, lowest_used} - pass format='json' for full structured data incl. the offers[] listing and images.

  Parameters:

  • ref (required) — string — Full Amazon product URL - pass the `url` from a glim_amazon_search result, or any /dp/<ASIN> product page URL. The URL carries the marketplace (amazon.de, amazon.co.uk, ...), so no separate region is needed; tracking junk in the URL is ignored. A bare ASIN is rejected: it is ambiguous across marketplaces.
  • format — string — Output format. 'text' (default): compact human-readable view, fewer tokens. 'json': the same product as machine-readable JSON, plus the fields text omits: the full `offers[]` list (text summarizes it), `images[]`, and variation/other-seller detail.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• glim_youtube_get read-only

  Fetch a YouTube video transcript from a video URL or 11-char id. The transcript is cleaned server-side: deduplicated, tags/HTML stripped, with coarse [m:ss] timestamps - roughly a tenth the size of the raw captions. Default format='text' returns it inline (when it fits ~40K chars / ~10K tokens) so a single call gives you the text directly; long-form videos fall back to a download_url note. Pass format='json' for the same transcript plus transcript metadata (video_id, canonical url, language, origin, size) and a presigned download_url - for batch/programmatic use. Default origin='uploader_provided' (human captions); falls back to 'auto_generated' automatically if missing (counts as 2 upstream calls). Cached 7 days server-side.

  Parameters:

  • ref (required) — string — YouTube video URL or 11-char video id (e.g. https://youtu.be/dQw4w9WgXcQ, https://www.youtube.com/watch?v=dQw4w9WgXcQ, or dQw4w9WgXcQ)
  • format — string — Output format. 'text' (default): the cleaned transcript inline as plain text (omitted with a download_url note when it exceeds the ~40K-char inline cap). 'json': the same cleaned transcript plus transcript metadata (video_id, canonical url, language, origin, size) and a presigned download_url - for batch/programmatic use. Both formats return the identical cleaned, deduplicated transcript.
  • origin — string — 'uploader_provided' for human captions (default), 'auto_generated' for YouTube auto-captions.
  • language_code — string — ISO 639-1 language code (e.g. 'en', 'de', 'fr')

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• glim_detect_ai read-only

  Detect AI-generated text. Scores any text for AI-authorship likelihood and returns an overall verdict (AI / human / mixed) with confidence, the AI/human/AI-assisted fractions, and a segment-by-segment breakdown showing exactly which parts read as AI-written - including per-segment humanizer flags (AI output run through paraphrasing/'humanizer' tools). Use it to verify whether content (comments, articles, profiles) is AI-generated, or to check text before publishing to see which segments would trip AI detectors - revise the flagged segments and re-check. Cost scales with text length: $0.06 per 100 words, rounded up, minimum $0.06. Max input 20,000 characters.

  Parameters:

  • text (required) — string — Text to analyze, plain text, 50+ characters, max 20,000. Detection reliability improves with length; very short texts return lower-confidence verdicts.
  • format — string — 'text' (default): compact human-readable report. 'json': structured data incl. per-segment text, scores, and humanizer flags.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• glim_telegram_search read-only

  Search Telegram: discovers public channels by name/topic (directory lookup) and finds indexed public post/channel pages (semantic web index scoped to t.me). Telegram has no global full-text search, so treat results as discovery: find the right channel here, then use glim_telegram_get(ref=<handle>) for its live posts or glim_telegram_get(ref, query=...) to search within that channel's full history.

  Parameters:

  • query (required) — string — Search query (topic, channel name, keyword)
  • kind — string — 'channels': channel directory lookup. 'posts': indexed t.me post pages. 'all' (default): both.
  • format — string — Output format. 'text' (default): compact human-readable view, fewer tokens. 'json': full structured data for machine parsing.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• glim_telegram_get read-only

  Fetch a public Telegram channel or post - no account or API key involved. Channel refs (@handle, handle, t.me URL) return channel info + recent posts newest-first with views, reactions, media, polls, and link previews; pass query to search within the channel's full history, and page older posts with before=<next_cursor>. Post refs (t.me/<channel>/<id>) return that post plus its most recent discussion comments. Media URLs are Telegram CDN links that expire within hours - fetch promptly, never store. Only channels with a public web preview work (most public channels); private channels and groups are not accessible.

  Parameters:

  • ref (required) — string — Public channel (@handle, handle, or t.me/<channel> URL) or post (t.me/<channel>/<id> or '<channel>/<id>')
  • after — string — Return posts newer than this message id
  • limit — integer — Max posts for channel refs (1-100)
  • query — string — Search within the channel's full history (channel refs only)
  • before — string — Return posts older than this message id (from next_cursor)
  • format — string — Output format. 'text' (default): compact human-readable view, fewer tokens. 'json': full structured data for machine parsing.
  • comment — string — Post refs: center the comment window on this comment id
  • include_comments — boolean — Post refs: include discussion comments (Telegram serves a small window of the most recent; walk older ones via comment=<oldest returned id>)

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.