Skip to main content
Glama
601,543 tools. Updated 2026-09-23 03:00

"A guide for conducting competitor analysis" matching MCP tools:

  • List a public/competitor creator's videos by platform + handle. Sort by 'recent' or 'top' (best-performing); optionally with analysis inline. Only returns creators already in the analysis library — for one you haven't ingested yet this returns reason="creator_not_in_library" with a next_step of analyze_creator(platform, username), not an error. When more videos exist beyond this page the response includes next_cursor — pass it back as cursor (same sort/filters) to fetch the next page; when next_cursor is absent you have everything.
    ConnectorOAuth
  • Get the full analysis (incl. scene breakdown) for a video — owned or public/competitor. Pass `platform` and `post_id` separately (the native post_id from analyze_post or list_videos — not the composite `id` field). Deep analysis runs async (~30-60s): right after analyze_post this returns {"status": "pending", "retry_after_seconds": N} — that is expected, not an error. Wait that long and call again until you get the full analysis. A genuine 404 means the post was never analyzed — call analyze_post(url) first.
    ConnectorOAuth
  • 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
  • Async extended variant of patent_landscape. Supports max_results up to 200 (vs 50 in sync mode) and an optional include_citation_graph flag that enriches each patent with its 2-level citation graph (parent patents that cite this one + child patents cited by this one). Returns immediately (<300ms) with a job_id. Poll the result with patent_landscape_result(job_id) after eta_seconds (~180s). Use for deep R&D white-space analysis, freedom-to-operate (FTO) audits, VC due diligence IP mapping, or large-scale competitor portfolio analysis. Async tool — register a webhook via `webhooks_manage(register, url, [job.completed])` to receive callbacks instead of polling. Faster + lighter.
    ConnectorNo auth
  • Async extended variant of patent_landscape. Supports max_results up to 200 (vs 50 in sync mode) and an optional include_citation_graph flag that enriches each patent with its 2-level citation graph (parent patents that cite this one + child patents cited by this one). Returns immediately (<300ms) with a job_id. Poll the result with patent_landscape_result(job_id) after eta_seconds (~180s). Use for deep R&D white-space analysis, freedom-to-operate (FTO) audits, VC due diligence IP mapping, or large-scale competitor portfolio analysis. Async tool — register a webhook via `webhooks_manage(register, url, [job.completed])` to receive callbacks instead of polling. Faster + lighter.
    ConnectorNo auth
  • Async extended variant of patent_landscape. Supports max_results up to 200 (vs 50 in sync mode) and an optional include_citation_graph flag that enriches each patent with its 2-level citation graph (parent patents that cite this one + child patents cited by this one). Returns immediately (<300ms) with a job_id. Poll the result with patent_landscape_result(job_id) after eta_seconds (~180s). Use for deep R&D white-space analysis, freedom-to-operate (FTO) audits, VC due diligence IP mapping, or large-scale competitor portfolio analysis. Async tool — register a webhook via `webhooks_manage(register, url, [job.completed])` to receive callbacks instead of polling. Faster + lighter.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Competitor Tracker & Co. watches your competitors' websites and reports what changed: pricing, product, messaging and corporate moves, crawled weekly and filed as a tagged, ranked report. This server gives your agent the same intelligence: subscribe to competitors, read the change feed, and pull page snapshots.
    MIT

Matching MCP Connectors

  • Two URLs in → 7-section comparative brief (positioning, pricing, feature gaps, messaging, tech stack, key differences) in under 3 minutes. Hosted on Apify, pay-per-use, no API keys required.

  • Track competitor brand demand across search, social and news. Free key at trendsapi.ai

  • Computes the on-page SEO score (0-100, graded S+ to D) of an article from its saved content: keyword checks (title, intro, meta, slug, subheading, density, image alt, cannibalization), sub-keyword or competitor-term coverage, and structure checks (length, meta and title length, subheadings, links, images, FAQ, paragraph and sentence length). When a done advanced analysis exists (run_advanced_seo_check) the competitor benchmark is included: competitor-relative score, topic gaps, recommendations and strengths. Pass locale to score a translation against its localized keyword (no benchmark or cannibalization check for translations). Returns every check with status good/ok/bad/na, the semantic keyword coverage and a prioritized list of fixes. The internal and external link checks are skipped when the website has no base URL set. Free and instant; nothing is modified. Pass website_id when the account has several websites (see get_account).
    ConnectorOAuth
  • Get a public/competitor creator's profile by platform + handle (e.g. instagram, 'natgeo'). Only returns creators already in the analysis library; it does not ingest. For a creator you haven't pulled in yet this returns reason="creator_not_in_library" (not an error) with a next_step of analyze_creator(platform, username) — call that (needs the content:ingest scope), wait for it to finish, then retry.
    ConnectorOAuth
  • Competitive gap analysis — scans two sites concurrently, shows side-by-side scores, category-by-category winners, competitive gaps (checks where the competitor scored 20+ higher), and generated overtake fix code with projected scores after closing gaps. Use this when the user wants to benchmark against a competitor or when scan_site detects competitors in the AI Identity Card. Pay per call ($3.00) via x402 — USDC on Base or Solana. On payment_required, the response includes the full x402 payload with payTo/amount/asset.
    ConnectorNo auth
  • Use when the user asks who competes with a company, what a competitor recently did, or for a competitive overview of a domain. Input a company domain or name and get a privacy-safe profile: firmographics, recent strategic moves (the existence of a shift + a was→now summary, with the real analysis date), and links to published reports/comparisons. Returns { covered: false } for companies IndustryLens doesn't publicly track.
    ConnectorNo auth
  • Returns an official GuruWalk support guide for a specific traveler-support topic. GuruWalk is a platform for free walking tours and paid activities; these guides are GuruWalk's own source of truth on how bookings, cancellations, account settings and contacting guides actually work, including current policies and the exact URLs travelers should use. These guides apply only to bookings and accounts on guruwalk.com. Available topics: - account_settings: The traveler wants to manage their GuruWalk account: edit their details (name, surname, phone, city, password), change their email, stop receiving emails / unsubscribe, or delete their account; or they can't access their account. These are concrete steps you shouldn't improvise: consult this before answering. - contact_guru: The traveler wants to contact or coordinate something with the guide of their GuruWalk booking, or thinks they are talking directly to the guide: they can't find them at the meeting point, the guide didn't show up, they're running late, they treat you as if you were the guide, ask for the tour photos, or ask about bringing a pet or paying the guide, or have a question only the guide can answer. - free_tour_modification: The traveler wants to modify or reschedule their GuruWalk free tour — change the day, time, language or number of people — or asks how to do it. - group_booking: The traveler wants to book or extend a GuruWalk booking for a group (they usually say how many; treat it as a large group from around 6 people), asks how to book for many people, can't book for the whole group, sees a large-group notice or is asked for a card or payment for the group, or had a booking cancelled as "group or duplicate". The rules aren't intuitive; consult this before advising. - paid_cancellation: The traveler wants to cancel or change a paid activity booked on GuruWalk, asks about a refund, or can't cancel from their account. Call this when the traveler raises a support topic covered above. Pass the exact topic; the guide content is returned.
    ConnectorNo auth
  • 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
  • Get competitor analysis data from AI search. Understand how you stack up against competitors across AI models. Every view is computed over `days` and, when given, only the prompts carrying `tag_ids` - so you can ask "how do we compare inside this one business line" in a single call. Views: - 'summary': Overview of competitive landscape. - 'arena': Prompt-by-prompt leaderboard across all competitors. - 'head-to-head': Direct comparison with one competitor (requires 'competitor' param). - 'by-model': Competitive performance broken down by AI model. - 'threats': Competitors gaining ground + opportunities where you're ahead. - 'heatmap': Competitor presence matrix across prompts and models. - 'over_time': Daily visibility for you and each competitor. This is the history behind the Competitive Trend chart, recomputed from stored daily results, so it is available for the whole window straight away rather than only from the day you started asking. Args: brand_id: The brand to check (required). view: Analysis view. Default 'summary'. competitor: Required for 'head-to-head'. On 'over_time' it narrows the response to you and that one competitor, including competitors outside the top slice. days: History window: 7, 14, 30 or 90. Default 30. period: A frozen calendar period (YYYY-MM or YYYY-Qn). When given, days is ignored and the response carries a `period` block. view='summary' only, and the shape differs: your_rank, rank_pool, your_visibility, competitors (each with prior_rank, prior_visibility, positions_gained, visibility_delta, new_in_list), notable_change, and perception_competitors. tag_ids: Optional. Comma-separated tag IDs from list_tags. Recalculates every metric over only the prompts carrying those tags. limit: 'over_time' only: how many competitor series to return, best ranked first. 1-50, default 10. response_format: 'concise' (default) trims wide matrices/leaderboards to a readable head to protect context; 'detailed' returns the full grid (still held under the response ceiling).
    ConnectorOAuth
  • Starts a competitor-relative SEO analysis of the default-language article: fetches the pages ranking in Google's top results for its target keyword, compares their depth and topic coverage with the article and stores a report (competitor-relative score, summary, topic gaps, recommendations, competitor terms, target word count). Asynchronous: returns as soon as the analysis is queued. It takes about 1 to 2 minutes; poll get_advanced_seo_report until status is done. The article must have a target keyword. Refused while an analysis is already running. Once done, check_article_seo_score and improve_article_seo use the benchmark automatically; re-run it only when the article changed substantially (see is_stale). Costs 1 AI brain credit, charged before the work, refunded if the provider fails. Requires an active subscription or free trial. Pass website_id when the account has several websites (see get_account).
    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
  • Get the free starting-point report for a project — a client-facing document assembled from setup-time data: positioning (niche + market profile), the site and its current content inventory, the curated competitor set, and early rising-topic signals. Free on every plan, no research run required. markdown is the ready-to-send render; the structured fields are the same data for custom rendering. lockedSections names the sections a research run adds (full opportunity map, 90-day sequence, competitor gap analysis) — absent here, not previewed. Once the project has a completed run, prefer get_pitch_report_payload: that is the full report.
    ConnectorNo auth
  • Decode a saved competitor ad into a reusable formula: hook, script, scenes, audio, call to action and style, plus a generation-ready recreation prompt. Requires a quote_id from estimate_ad_cost with kind "decode" (a flat price). Credits are charged only when the analysis succeeds; an ad decoded before returns its stored decode and charges nothing. SIGN-IN REQUIRED: connect this server with OAuth (the host prompts for it), or add an API key header "Authorization: Bearer acd_live_…" created at https://aicontentdrop.com/settings/integrations.
    ConnectorNo auth
  • Read a template in full: its blueprint plus its `description` — the markdown usage guide (what it is, how to use it, which business rules to fill). The guide IS the underlying model's FINANCE.md (a template's id equals its model id): to edit a template's guide, edit that model's FINANCE.md via layerz_set_finance_md — it propagates live, not as a snapshot. After forking or applying a template, follow the guide and update the new model's FINANCE.md so the conventions and objective match the project. Account-level, read-only.
    ConnectorOAuth
  • Get the caller's OWN content profile / DNA (topics, pillars, voice) synthesized from their content. Scoped per account group (brand): pass a group_id from list_accounts, or omit it for the default group. There is no per-creator content-profile tool — for competitor analysis use get_creator + list_creator_videos.
    ConnectorOAuth