Skip to main content
Glama

MentionedOn Visibility and Website Fixes

Verify installed website fixes

verify_website_fixes

Needs a connected MentionedOn account with a paid or 7-day trial monitoring slot (Local is $99/month). Use after the user installs the fixes: fetches one page on the business's own website and checks it for the saved schema and text, saving found, not-found or unknown results against that revision. Up to 20 website checks a day. A found fix does not prove better AI visibility.

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>",
      "revision": "<revision>",
      "url": "<url>",
      "authorizationAcknowledged": "<authorizationAcknowledged>"
    },
    "name": "verify_website_fixes"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage on the owned domain where the fixes are installed.
revisionYesInteger from get_website_fixes.
businessIdYesBusiness id returned by list_monitored_businesses.
authorizationAcknowledgedYestrue once the user confirms they own or may check this website.

Output Schema

NameRequiredDescriptionDefault
recordYes
nextStepYes
businessIdYes
limitationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / authorizationAcknowledged / description
      Added value: +"true once the user confirms they own or may check this website."
    • addedInput schema / properties / revision / description
      Added value: +"Integer from get_website_fixes."
    • addedInput schema / properties / url / description
      Added value: +"Page on the owned domain where the fixes are installed."
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false) it discloses the billing/plan gate, the daily quota, the fact that a result is written against a specific revision, and the important epistemic caveat that 'a found fix does not prove better AI visibility'. The one unstated trait is that a check consumes a slot even when the result is unknown, which affects retry decisions.

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

Conciseness5/5

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

Three dense sentences with no filler: eligibility, action and persisted result, then quota and caveat. Prerequisites are front-loaded, which is appropriate for a gated tool, and the caveat lands last where it is most likely to be read.

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?

For a non-idempotent, quota-limited, open-world check with four required parameters, the description covers gating, timing, side effects and expectation-setting, while the output schema handles return structure. Nothing an agent needs in order to call it safely 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 description coverage is 100%, so the baseline is 3. The description only lightly reinforces the schema by tying the fetch to 'one page on the business's own website' and the revision to the saved fix set; it adds no new constraints or formats beyond what the schema already states.

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?

States a specific verb and resource: 'fetches one page on the business's own website and checks it for the saved schema and text'. This clearly separates it from sibling get_website_fixes (which returns the revision) and draft_website_fixes (which produces fixes), and it names the persisted outcome (found/not-found/unknown against a revision).

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

Usage Guidelines5/5

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

Gives explicit sequencing ('Use after the user installs the fixes') plus hard prerequisites: a connected MentionedOn account and a paid or 7-day trial monitoring slot with the Local price noted. It also states the operational ceiling ('Up to 20 website checks a day'), so an agent knows both when to call it and when not to.

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