Skip to main content
Glama

MentionedOn Visibility and Website Fixes

See visibility evidence and changes

get_visibility_report
Read-onlyIdempotent

Needs a connected MentionedOn account. Use when the user asks how their business shows up in AI answers: returns the latest saved check (score, mention and citation rates, answer excerpts per assistant, competitors, cited sources) and up to 30 earlier checks, with dates, provider gaps and a score change only when checks are comparable. Needs businessId from list_monitored_businesses. Read-only; runs no new scan, so results are dated, not live.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "businessId": "<businessId>"
    },
    "name": "get_visibility_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many saved checks to return, newest first (default 30).
businessIdYesBusiness id returned by list_monitored_businesses.

Output Schema

NameRequiredDescriptionDefault
latestYes
statusYes
byModelYes
historyYes
baselineYes
businessYes
evidenceYes
nextStepYes
reportUrlYes
competitorsYes
improvementYes
limitationsYes
scoreChangeYes
recommendationsYes
evidenceTruncatedYes
improvementHistoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"How many saved checks to return, newest first (default 30)."
  2. Changed5 schema fields changed
    • addedOutput schema / properties / business / properties / monitoring
      Added value: +{
      +  "enum": [
      +    "live",
      +    "paused",
      +    "plan_limit",
      +    "off",
      +    "payment_failed"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / business / required
      Previous value: -[
      -  "id",
      -  "name",
      -  "website",
      -  "active",
      -  "onboardingStatus"
      -]New value: +[
      +  "id",
      +  "name",
      +  "website",
      +  "active",
      +  "monitoring",
      +  "onboardingStatus"
      +]
    • addedOutput schema / properties / nextStep
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / status / enum
      Previous value: -[
      -  "ready",
      -  "awaiting_baseline"
      -]New value: +[
      +  "ready",
      +  "awaiting_baseline",
      +  "awaiting_checkout",
      +  "plan_required",
      +  "payment_failed"
      +]
    • changedOutput schema / required
      Previous value: -[
      -  "business",
      -  "status",
      -  "latest",
      -  "baseline",
      -  "scoreChange",
      -  "history",
      -  "byModel",
      -  "competitors",
      -  "evidence",
      -  "evidenceTruncated",
      -  "recommendations",
      -  "improvement",
      -  "improvementHistory",
      -  "reportUrl",
      -  "limitations"
      -]New value: +[
      +  "business",
      +  "status",
      +  "nextStep",
      +  "latest",
      +  "baseline",
      +  "scoreChange",
      +  "history",
      +  "byModel",
      +  "competitors",
      +  "evidence",
      +  "evidenceTruncated",
      +  "recommendations",
      +  "improvement",
      +  "improvementHistory",
      +  "reportUrl",
      +  "limitations"
      +]
  3. Added

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnly/idempotent/non-destructive annotations it discloses the auth prerequisite, that results are dated rather than live, that score change is reported only when checks are comparable, and that provider gaps may exist. Those are exactly the operational caveats an agent needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but front-loaded: prerequisite, then trigger, then payload, then the read-only caveat. The long parenthetical return list is informative rather than filler, though it slightly duplicates the output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Prerequisites, trigger, payload shape, comparability caveat and staleness are all covered for a two-parameter read tool. Nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented, and the description mostly restates the businessId provenance and the 30-check ceiling. Baseline 3 applies since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb+resource and enumerates exactly what comes back: latest saved check (score, mention and citation rates, answer excerpts per assistant, competitors, cited sources) plus up to 30 earlier checks. An agent can distinguish this from build_visibility_action_plan or summarize_scan_evidence without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete trigger ("Use when the user asks how their business shows up in AI answers") and prerequisites (connected MentionedOn account, businessId from list_monitored_businesses). It implicitly rules out scan-running siblings via "runs no new scan," but never names an alternative tool explicitly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources