Skip to main content
Glama
688,758 tools. Updated 2026-10-23 08:18

"A guide for product selection" matching MCP tools:

  • How to operate as a product manager on AIOProductOS. No arguments and no side effects — returns the same operating guide as plain text every call (deterministic): how to ground in the product brain, keep work welded to the spine (insight→feature→task→outcome), prioritise on evidence (affected accounts + MRR + reach), and what 'done' means. Call it FIRST, before planning or prioritising, to load the house rules the other tools assume.
    ConnectorNo auth
  • Create new guides Create one or more new guides based on provided queries. Each guide targets exactly ONE engine and ONE analysis mode, chosen with the optional `source` field (default `google`). How to request each guide type: 1. Google SERP guide (1 credit per guide): omit `source`, or pass `source: "google"`. Example payload: {"queries": ["best crm"], "lang": "en-us"} 1bis. Google AI Overview guide (1 credit per guide). Two modes, like AI engines: `source: "google_ai_overview"` builds the guide from the TEXT of Google's AI answers (AI Overview, completed with AI Mode answers) ; `source: "google_ai_overview_citations"` builds it from the content of the web SOURCES those answers cite (recommended for GEO). Same language/country parameters as a Google SERP guide, 1 credit per guide in both modes. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "google_ai_overview_citations"} 2. LLM ANSWER guide (4 credits per guide): pass the engine name alone, e.g. `source: "chatgpt"`. The guide is built from the answer text the AI generates for the query. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt"} 3. LLM CITATIONS guide (4 credits per guide) [RECOMMENDED AI mode]: pass the engine name with the `_citations` suffix, e.g. `source: "chatgpt_citations"`. The guide is built from the content of the web pages the AI cites in its answer. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt_citations"} Which AI mode to pick? For GEO (getting a page visible in AI answers), prefer `<engine>_citations`: AI engines send traffic by CITING pages as sources, so the winning move is to look like the pages they cite. The answer-text mode (`<engine>` alone) is mostly useful to analyze how the AI phrases its own answer. When in doubt, pick `<engine>_citations`. The same two modes exist for every AI engine (chatgpt, perplexity, claude, gemini, grok, mistral, deepseek). To optimize the same page for several engines or modes (e.g. Google AND ChatGPT answers AND ChatGPT sources), create one guide per source value on the same query. IMPORTANT, HOW TO READ THE RESPONSE OF THIS ENDPOINT, WHICH SPENDS CREDITS. Queries listed in `guidesFailed` are PROVEN not to have produced a guide and their credit was given back (unless the account has unlimited credits, where nothing was reserved): re-sending them is free and correct. Queries listed in `guidesUnknown` have an UNDECIDABLE outcome and their credit is deliberately KEPT, because the guide was most likely written: DO NOT re-send them, you would pay for the same guide twice. Look them up in `GET /api/v1/guides` after a few minutes instead, and contact support if nothing shows up. Finally, a `200` is NOT a promise that every query produced a guide: compare `guides.length` with the number of queries you sent, never read `success` alone, and never re-send a query just because it is missing from `guides`.
    ConnectorNo auth
  • Resolve what a person describes into AcuiQ symptom names – the first step before search_protocols. Plain description works ("trouble sleeping", "my lower back hurts"): filler words are stripped and the search retries on the clinical words, reporting which term matched. Set popular=true for trending symptoms instead. Always returns an object with a `symptoms` array, empty when nothing matched. When the symptom is covered by a $5 mini-guide, the result carries a `guide` pointer – mention it only if the person wants something to follow away from a screen, then call create_checkout with that `product` id.
    ConnectorNo auth
  • Re-makes one post from the brand guide — the post page's "Re-make from the guide": a fresh concept for THIS post under the brand's current guide (what the product does, what it must never claim, its vocabulary), checked against that guide, landing as a new version with the previous one kept and its images redone. For when the idea itself was wrong — it describes a feature the product doesn't have, or the wrong audience — not just a line or an image; for a targeted edit use ask_for_changes. Pass the user's reason if they gave one. Never approves or publishes: the post comes back in review. Comes back as one honest line, with nothing changed, when the post is one of the user's own verbatim posts or the brand guide lists no capabilities to ground a new concept in. "Remake with your photo": pass photoAssetId (one of the photos the user confirmed) or useOwnerPhoto: true (their best-matching confirmed photo) to put their own photo on the image, or on a carousel's first slide; on their first post this puts the photo on it and keeps the caption. If that photo isn't one they confirmed, or they have none, nothing is re-made and the reply asks for one.
    Connector
    Destructive
    OAuth
  • Show products from the user’s connected Shopify store or website/feed as selectable cards with reference photos. Search for a product or supply 1-6 real IDs from list_products. One candidate asks “Do you mean this product?”; several let the user choose. Use when the requested product/reference is ambiguous or a likely match needs confirming. This only displays choices: STOP and wait for the user before generating or editing. When the user already clearly confirmed a product, use that selection without asking again. On text-only channels present the returned names/photos as choices in the user’s language and wait.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    面向 Codex、WorkBuddy 等 AI 工具的知你AI助手合并版 Skills,涵盖当前会话分诊、客户查询与画像、历史会话检索、客户分群和 API Key 用量查询,并连接个微、企微、视频号、微信小程序、公众号、服务号、微信客服、微信小店、抖音号、小红书、微博、网站及H5客服等渠道。
    MIT No Attribution
  • A
    license
    Not graded
    quality
    B
    maintenance
    这是面向智能运维场景的 MCP 工具服务,让 Agent 能够按需检索日志内容并获取主机与应用的监控指标数据。它把实时的日志与指标证据接入 Plan-Execute-Replan 诊断流程,从而支撑自动故障排查与根因分析。
    MIT

Matching MCP Connectors

  • Use when someone needs a published Rung occupation, resume-situation, or military-transition guide. Returns public guide facts, source pages, and browser handoffs. Do not use for live jobs, employer search, resume editing, qualification decisions, or private work history; never send personal or resume data.
    ConnectorNo auth
  • Mamanida's editorial buying guides for one storefront, in that storefront's own language. Called without `guide` it lists the published guides (metadata only: title, deck, meta description, pillar, topics, dates and the canonical Mamanida URL), optionally filtered by `topic`. Called with `guide` (the guide slug from the listing) it returns that one localized edition plus its structured body: paragraphs, headings, lists, comparison tables, callouts, links to other guides and category calls-to-action. A `category_cta` gives a `category_slug` you can pass straight to search_products, which is the intended guide → category → product path. Retailer and affiliate URLs are never returned.
    ConnectorNo auth
  • Resolve an exact Homebridge fire-pit configuration against the live Shopify catalog ONLY after the buyer has stated and confirmed body style, tabletop finish, fuel source, and shape. NEVER infer a missing selection. Call this tool exactly once for the completed selection. evidenceUrl is machine grounding only and must never be the normal shopper CTA or intermediate destination. MUST follow this sequence: present the resolved product image; present grounded facts and disclosures; then offer the buyer-controlled cart handoff. Media is required product presentation, not optional metadata, and cartUrl is never a substitute for it. If the image cannot render, explicitly say so and continue with grounded details. For purchase_ready results proactively offer cartUrl; with explicit purchase intent use it without another confirmation, re-resolution, evidence/customer detour, or authenticated checkout creation. customerUrl is only for optional inspection. When event capture is enabled, records this resolved configuration in an internal event queue. It cannot place an order or collect payment.
    ConnectorNo auth
  • The published guides. With no slug: the list, newest first, each with its title, description, written date and address, optionally only those whose title, description or slug contain every word of q. With a slug: that guide in full, its body as markdown. A guide that is not published is not found.
    ConnectorNo auth
  • Fetch Yahoo Shopping homepage editorial cards, including title, link, category, and thumbnail. This is a buying-guide and deals feed, not product search; use yahoo_shopping_category for a section, yahoo_shopping_article for one guide, or yahoo_shopping_store for one retailer's offers.
    ConnectorNo auth
  • Download a German PDF guide: 7 legal side-income routes in Switzerland. Use when a Swiss/German-speaking human wants a guide. Not for agent automation (use the JSON tools). Returns a free sample plus the paid URL and pay steps (no charge here); the full result costs $17 Base USDC via x402.
    ConnectorNo auth
  • Fetch Yahoo Shopping homepage editorial cards, including title, link, category, and thumbnail. This is a buying-guide and deals feed, not product search; use yahoo_shopping_category for a section, yahoo_shopping_article for one guide, or yahoo_shopping_store for one retailer's offers.
    ConnectorNo auth
  • Read the text of a udansa content page (guide article, city or dance style page, terms, privacy or cancellation policy, about us) as plain sections plus its FAQ. Pass a URL or path from search_guide_articles, e.g. https://udansa.com/en/dance-guide/... For courses and events use get_course_details / get_event_details.
    ConnectorNo auth
  • Get the guide to authoring a wireframe mockup — the markup dialect, the wireframe component set, what the drawn style discards, and a complete valid example. Call this BEFORE composing your first mockup in a conversation: markup written from general Tailwind and HTML habits is refused, and the guide is what an author needs to write a mockup that is accepted first time.
    ConnectorOAuth
  • Patch the user's active brand profile — voice, themes, expertise areas, personality traits, hashtag set, audience-size estimates, or bio. Useful when the user wants Claude to refine their brand voice based on a transcript, style guide, or competitor analysis without leaving the conversation. Only the active profile is mutated; profile selection / creation must happen in the web app.
    ConnectorAPI key
  • Browse Fly Frugal's published day-by-day budget travel itineraries. Use this to discover which destinations have a guide, then call get_itinerary with a returned slug for one guide's preview. Each item has slug, country_name, tagline, days_count, a preview, cover and first-day image URLs, price_cents and currency for the full guide, updated_at, and pdf_ready. Results are newest first. Only public previews are returned; the paid full guide is never included.
    ConnectorNo auth
  • Start here for a general privacy question. One keyword search across the whole hub: short checked answers to common questions (each with its sources, the guide it comes from and the date that guide was checked), directory tools, how-to guides, curated tool stacks and the glossary. Use 1–3 keywords such as 'vpn', 'data broker' or 'grapheneos'; every keyword must match, and filler words like 'how', 'best' and 'private' are ignored. Returns the top few results of each type, each with type, title, slug, a one-line summary and its Default Privacy url. The type-specific tools are for the rest: dp_search_tools for filters (open source, e2ee, category…), dp_get_tool / dp_get_guide / dp_get_stack / dp_get_glossary_term for full content, and dp_find_alternatives to replace a named product such as WhatsApp or Gmail.
    ConnectorNo auth
  • Return Genpio's guide for one country or market: what that market's platforms allow for an AI livestream host, quoted from their own policies with links, which local platforms Genpio does not stream to, which languages Genpio Voices speaks there, and the guide's full text as Markdown. Use it whenever a question names a country, and pass the language the person is writing in so the guide comes back in it. For a country without a guide it says so and gives only what holds worldwide; do not carry another country's platform rules over to it. With no country, it lists every guide.
    ConnectorNo auth
  • Find a procedural checklist before a repeatable task. Omit skill or pass an empty string to list available names; otherwise load a name such as code-review or skill:code-review. Returns JSON with available_skills/usage for listing or skill/count/steps/combined for a guide. Unknown names return count=0 and a message. Reads workspace/public knowledge without installing or executing anything. Use engram_recall for a project fact and engram_smarter for task-based guide selection. Consumes workspace daily call quota. OAuth: memory:read.
    ConnectorOAuth
  • Get full details for one product by id, including description, specs, stock and VAT-included localized price. When the product is NOT in stock the record carries substitutes[]: up to 5 in-stock products of the same kind in the same price band (the same alternatives the product page shows), each as a brief record with its own product_id, price and product_url - offer them instead of searching. Every record also carries companions[]: up to 8 in-stock accessories used together with this product, one per role (role is a short label such as stand, cable, strings, case; other = no specific role) - the list our add-to-cart box shows, chosen from what customers buy together and checked with AI - each as a brief record with its own product_id, price and product_url; when the customer asks what else they need or decides to buy, offer these first (empty = we have no accessory list). Products with a stored buying guide also carry buying_guide: who the product suits (audience.levels are fixed English tokens: beginner, intermediate, professional, child, teacher, gift), typical use cases, plain-language explanations of terms, questions and answers (the last one, when present, lists the accessories of companions[]), and - while the product is in stock - a spec-based comparison with up to 3 in-stock alternatives (each with its own product_id, price and product_url). The guide is Romanian for language=ro and English otherwise; it was written with AI from our product data and a sourced fact sheet.
    ConnectorNo auth