Skip to main content
Glama

MentionedOn Visibility and Website Fixes

Inspect your business website

inspect_business_website

Needs a connected MentionedOn account with a paid or 7-day trial monitoring slot (Local is $99/month). Use first when fixing business information: fetches a few public pages of the saved business website and saves candidate facts with where each was found. Pass revision from get_website_fixes (0 if none) and authorizationAcknowledged: true once the user confirms they own the site. Saves a new revision; refused once drafts exist; up to 20 website checks a day. Runs no AI scan and publishes nothing.

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>",
      "authorizationAcknowledged": "<authorizationAcknowledged>"
    },
    "name": "inspect_business_website"
  }
}

Input Schema

NameRequiredDescriptionDefault
revisionYesInteger from get_website_fixes (the current saved revision); use 0 when no record exists.
businessIdYesBusiness id returned by list_monitored_businesses.
authorizationAcknowledgedYestrue once the user confirms they own or may inspect this website.

Output Schema

NameRequiredDescriptionDefault
recordYes
nextStepYes
businessIdYes
limitationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / authorizationAcknowledged / description
      Added value: +"true once the user confirms they own or may inspect this website."
    • changedInput schema / properties / revision / description
      Previous value: -"Exact saved revision returned by get_website_fixes; use 0 when no record exists."New value: +"Integer from get_website_fixes (the current saved revision); use 0 when no record exists."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only flag it as a non-read-only, non-idempotent, open-world write; the description adds the substance: it writes a new revision, is refused if drafts exist, is capped at 20 website checks per day, requires an ownership acknowledgment, and neither runs an AI scan nor publishes anything. Those facts materially change how an agent plans and retries calls, and nothing conflicts with the annotations.

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?

Four dense sentences, front-loaded with the prerequisite and the "use first" routing before mechanics and limits. Nearly every clause carries information; only the parenthetical pricing and the redundant restatement of the revision source keep it from being maximally tight.

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 three-parameter write tool with an output schema already describing returns, the description covers prerequisites, ordering, rate limits, refusal conditions, authorization, and side effects. An agent has everything needed to decide whether it may call and what happens when it does.

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 all three parameters are already documented, and the description largely restates them (revision from get_website_fixes, authorizationAcknowledged after user confirmation). It adds workflow meaning to revision but no format or validation detail beyond the schema, so the baseline 3 applies.

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 concrete verb and resource: "fetches a few public pages of the saved business website and saves candidate facts with where each was found." It also distinguishes itself from the sibling fixes tools by declaring "Use first when fixing business information," so an agent can place it in the workflow without opening other schemas.

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 ordering ("Use first when fixing business information"), a prerequisite (connected account with a paid or trial monitoring slot), the source of the revision value (get_website_fixes, 0 if none), and a hard exclusion ("refused once drafts exist"). This is when/when-not/where-to-get-inputs guidance in one compact block.

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