"A guide to creating videos" matching MCP tools:

• get_productA

  Tolstoy ShopperA

  Load full details for one product by its `productRef` (from search_products or browse_products): description, price, media, the brand's real product videos, size guide, per-variant stock, and buy links. Returns each variant's id and options (size/color). Use it to resolve the exact `variantId` the shopper wants before calling build_cart, and to answer fit/sizing questions from the size guide. The response includes the product image so it can be seen directly.

  ConnectorNo auth

• create_guidesA

  serpmanticsA

  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

• get_guideA

  VeteranHQA

  Use this when a slug from search_guides names the guide a veteran needs and the answer should carry what the guide says. Returns the slug, title and summary, the date the facts in it were last verified against its sources, the public URL of the guide on veteranhq.app, the body split into the sections the guide itself defines, each with a heading and its text, and the sources the guide cites, each with a title and a URL. A slug this library does not hold returns a tool error carrying GUIDE_NOT_FOUND, whose message says to call search_guides and use a slug from its results. A guide longer than one result can carry returns the sections that fit, plus omittedSections counting the sections left out and a note stating that count and the guide URL. A single section larger than the whole budget is served shortened at a paragraph or sentence boundary, with truncatedSection naming its heading and the note repeating it, so a section that was cut is distinguishable from one served whole. Those three fields are absent when the whole guide is returned, so a shortened answer is distinguishable from a complete one. A guide states the rules as VeteranHQ read them from the cited sources on the date it reports, and VA decides a claim. It reads no account data, so the answer is the same for every caller with the same inputs.

  ConnectorNo auth

• find_videosA

  KlyfA

  SEARCH the signed-in user's own YouTube catalogue and LIST the videos that match, by what is written in their titles, descriptions and tags. This is RETRIEVAL, not ranking: call it whenever the user wants to FIND or LIST videos rather than judge them. Use it for 'which of my videos are about X', 'show me every video where I talked about X', 'find my videos mentioning X', 'which videos have a referral or affiliate link in the description', 'list all my videos', 'what have I made about X', or any question whose answer is a SET of their videos. Also use it to pull ONE video's full record (its complete description, tags, length, views): pass that video's title as `video`. Leave everything empty to browse the whole library newest first. Results are paginated: each answer says how many matched and the `offset` to pass to see the next page, so keep asking to walk a large catalogue rather than stopping at the first page. It searches only what the creator WROTE, never what is spoken in the video. For how a video PERFORMED use analyze_video; for the best performers use find_best_videos. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.

  ConnectorOAuth

• get_guidesA

  Mamanida Maternity CatalogueA

  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

• get_personalization_guideA

  SliqA

  Return the user's personalization guide — how they want a person researched before you write to them. Call this only when you are going to personalize a message; follow the returned guide. When none is set, returns a note and you should fall back to the default research rules in the outreach craft skill.

  ConnectorOAuth

• guidesA

  Ownware CatalogueA

  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

• read_guideA

  Recipes DailyA

  Read the full text of a cooking guide from recipes-daily.com, as markdown. Call this when search_recipes lists a guide that answers the question — how or why something works in the kitchen, how to store or substitute an ingredient, how to use a piece of equipment — and answer from what it says rather than from memory, citing its URL. Pass the guide URL exactly as search_recipes returned it. For recipes, use show_recipes instead: a recipe is a page the person cooks from, not text to retell.

  ConnectorNo auth

• search_videosA

  SocialGPTA

  Semantic search over your own ANALYZED videos — those with a completed deep analysis — ranked by relevance to the query. Prefer this over list_videos when you want videos matched by what's actually in them (hooks, scenes, topics) rather than by caption text. Returns {"videos": [...]}; an empty list carries a reason (no_connected_accounts → connect_url, or no_matching_videos). When more matches exist beyond this page the response includes next_cursor — pass it back as cursor (same query/filters) to fetch the next page; when next_cursor is absent you have everything.

  ConnectorOAuth

• ask_videoA

  RekaA

  Ask a question about one or more videos with visual analysis. Most effective on focused time ranges — use start/end to specify the segment to analyze. BEFORE calling this tool, read the reka://docs/guide resource for recommended workflows. In most cases, you should first: - search_videos to find WHEN something happens, then pass those timestamps here as start/end - segment_video to detect and locate specific objects - get_transcript to read what was said For single-video questions, pass video_id with start/end. For cross-video questions, pass videos — a list of video references with start/end each. For follow-up questions, pass conversation_id from the previous response. You can add start/end to drill into a specific moment while keeping the conversation context. Requires qa_only or full pipeline.

  ConnectorNo auth

• mockup-guideA

  dot•requirementsA

  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

• list_itinerariesA

  Fly Frugal Travel DataA

  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

• list_similar_videosA

  SocialGPTA

  Find public/competitor videos similar to a reference video, by content embedding. Identify the reference video by platform + post_id (its native id from list_videos / get_video). Returns {"videos": [...]}; if the reference post can't be used yet (no embedding) or isn't found, it returns an empty list with a `reason` rather than erroring.

  ConnectorOAuth

• get_use_caseA

  FutureSmart AI DemosA

  Full use-case detail as a JSON+Markdown envelope: step guide, pros/cons, FAQ, tools used (JSON) + the full narrative guide (Markdown, full_md). null if unknown. Pass `fields` to project to only the keys you need (token-efficient).

  ConnectorNo auth

• get_guideA

  Homechecker GuidesA

  Retrieve one canonical Homechecker guide by slug. Use a slug returned by list_guides or search_guides. Returns source links, review metadata, method and limitations with the guide.

  ConnectorNo auth

• list_videosA

  vivideoA

  List the account's videos, newest first. Filter by status and limit the count to keep responses small.

  ConnectorNo auth

• place_photosA

  API DirectA

  Get photos and videos of a Google Maps place by place_id (from search_places). Returns standard and large URLs, coordinates and capture time; photos and videos come mixed, so filter on the type field. Up to 10 items per page. Billed $0.01 per page.

  ConnectorNo auth

• lint_specA

  RoutebaseA

  Validate an API specification against style guide rules. Returns violations grouped by severity (error, warning, info) with rule details and affected paths. Use this to check against style guide rules; to check against the OpenAPI standard use validate_spec. Requires project context.

  ConnectorAPI key

• get_guideA

  TessryxA

  Fetch a Tessryx guide by topic (markdown). Use list_guides to see the available topics. Reach for the relevant guide before authoring to avoid trial-and-error.

  ConnectorOAuth

• buy_guideA

  DéstaireA

  Buy a city guide for the user, paid inside this conversation. Gives a pay link that takes an MPP payment (a Stripe Shared Payment Token from your wallet, such as Link). Confirm the user's email first: the guide goes to that account, and the purchase is final.

  ConnectorNo auth

• guides_createA

  ZernoteA

  Create the first interview guide on a project. Use this to upload a new guide. Pass structured fields, not markdown: intro, blocks (title, minutes, notes, questions with text/note/key), and notes_template. Needs at least one block with a title. Fails if the project already has a guide — then use guides_edit. Core does not show the guide. Live reads it on the project.

  ConnectorOAuth