← GoVISIBLECONTENT HISTORY
WHAT CHANGED
Update to GoVISIBLE
Snapshot Oct 24, 2026 · 13:44 UTC · version 1.0.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save GoVISIBLE and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use when the user asks about their brand's AI visibility, GEO (generative engine optimization), mention strength, sentiment, share of voice, citations, buyer prompts, AI answers, competitor visibility, or a GoVISIBLE audit or monthly report. Retrieves read-only data from the connected GoVISIBLE account and explains it without inventing metrics.",
"included_files": [],
"name": "govisible",
"skill_md_contents": "---\nname: govisible\ndescription: Use when the user asks about their brand's AI visibility, GEO (generative engine optimization), mention strength, sentiment, share of voice, citations, buyer prompts, AI answers, competitor visibility, or a GoVISIBLE audit or monthly report. Retrieves read-only data from the connected GoVISIBLE account and explains it without inventing metrics.\n---\n\n# GoVISIBLE\n\nUse the connected GoVISIBLE MCP server to answer questions about how brands appear in AI-generated answers. All tools are read-only and return only data the signed-in GoVISIBLE account can access.\n\n## When not to use\n\n- Do not use GoVISIBLE tools for requests unrelated to AI visibility, GEO, or the user's GoVISIBLE projects.\n- GoVISIBLE cannot create, edit, or delete projects, run new benchmarks, change settings, or process payments. Say so instead of calling a tool.\n- Never try to access or describe data from another customer's GoVISIBLE account.\n\n## Choose the project first\n\n1. Most tools need a `projectId`. If the user has not identified a project, call `list_projects`.\n2. If exactly one project matches the brand the user named, use it. If several match or none is named, ask the user which project to use.\n3. Use `get_brand_info` when you need the project's brand profile, tracked competitors, or configured AI engines.\n\n## Pick the right tool\n\n| User asks for | Tool |\n| --- | --- |\n| Overall visibility | `get_visibility` |\n| Visibility by AI engine, date, cluster, journey, persona, intent, or competitor | `get_visibility_by_AiEngine`, `get_visibility_by_date`, `get_visibility_by_cluster`, `get_visibility_by_journey`, `get_visibility_by_persona`, `get_visibility_by_intent`, `get_visibility_by_competitors` |\n| Mention strength | `get_mention_strength` and its `_by_` variants |\n| Sentiment | `get_positive_sentiment`, `get_negative_sentiment` and their `_by_Clusters` / `_by_AiEngines` variants |\n| Share of voice | `get_ShareOfVoice`, `get_ShareOfVoice_by_Clusters`, `get_ShareOfVoice_by_AiEngines` |\n| Citations, cited websites, pages, and domains | `get_citations`, `get_citation_domains`, `get_websitecitation_share`, `get_websitecitation_pages`, `get_page_intelligence` and related citation tools |\n| Competitor leaderboard | `get_competitors_analysis` |\n| Buyer prompts and per-prompt results | `list_prompts`, `get_prompt_data`, `get_prompt_drilldown` |\n| Raw AI answers and their citations | `list_ai_answers` |\n| Benchmark run history and KPI trends per run | `list_runs`, `get_brand_run_metrics` |\n| Complete audit report | `get_audit_report` |\n| Monthly report for a calendar month | `get_monthly_report` |\n\nPrefer one report tool (`get_audit_report` or `get_monthly_report`) over stitching many metric tools together when the user asks for a report.\n\n## Dates and filters\n\n- Omit `startDate` and `endDate` unless the user asks for a specific period. The default window is the last calendar month of completed benchmark runs.\n- Pass dates as `YYYY-MM-DD` only when the user asks for a custom range.\n- Preserve every filter the user gives: date range, AI engine, cluster, journey, persona, intent, and competitors.\n\n## Presenting results\n\n- State the project, reporting period, and filters that the tool returned.\n- Lead with the most relevant metrics, then supporting detail.\n- Keep measured GoVISIBLE data separate from your interpretation or recommendations.\n- Keep answers concise unless the user asks for a detailed analysis.\n\n## Accuracy\n\n- Treat tool results as the only source of GoVISIBLE metrics. Never invent, estimate, or fill in missing values.\n- If a tool returns an error, no data, or a truncated result, say so plainly and suggest a narrower date range or a different filter.\n- If the connection is not authorized, ask the user to reconnect GoVISIBLE. Never ask for or repeat passwords, OAuth tokens, or API keys.\n"
}SHA-256 of public snapshot: 6d01c8cfd86c30f189d76c7d882ccaeecfddb3d0075b3367ebd2bb52f18008b5