Skip to main content
Glama

MentionedOn Visibility and Website Fixes

Prepare confirmed website fixes

draft_website_fixes

Needs a connected MentionedOn account with a paid or 7-day trial monitoring slot (Local is $99/month). Use after the user confirms the facts from inspect_business_website: generates and saves business schema, website copy and a business-profile description from those facts only. Pass the current revision and confirmed: true; never invent missing facts. Saves a new revision; no AI model cost, nothing is published or sent.

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>",
      "facts": "<facts>",
      "businessType": "<businessType>",
      "confirmed": "<confirmed>"
    },
    "name": "draft_website_fixes"
  }
}

Input Schema

NameRequiredDescriptionDefault
factsYesBusiness facts the user confirmed, from the inspection.
revisionYesInteger from get_website_fixes (the current saved revision); use 0 when no record exists.
confirmedYestrue once the user has reviewed and confirmed these facts.
businessIdYesBusiness id returned by list_monitored_businesses.
businessTypeYesschema.org business type for the generated schema.

Output Schema

NameRequiredDescriptionDefault
recordYes
nextStepYes
businessIdYes
limitationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / businessType / description
      Added value: +"schema.org business type for the generated schema."
    • addedInput schema / properties / confirmed / description
      Added value: +"true once the user has reviewed and confirmed these facts."
    • addedInput schema / properties / facts / description
      Added value: +"Business facts the user confirmed, from the inspection."
    • 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.8/5.0
Behavior5/5

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

Goes well beyond the annotations: it names the account/plan prerequisite, the write effect (saves a new revision), the absence of AI model cost, and that nothing is published or sent. That complements readOnlyHint=false and idempotentHint=false with the practical consequences an agent needs.

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 every clause carries information: prerequisites, sequencing, argument constraints, and side effects, with no filler. The trade-off is that the first sentence is prerequisites rather than purpose, so the 'what' arrives slightly late, though the title mitigates this.

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 mutating tool with a nested facts object, the description covers preconditions, ordering, argument discipline, side effects, and cost, and an output schema exists so return values need no explanation. Nothing an agent needs in order 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.

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description still adds meaning: revision must be the current saved revision, confirmed must be true, and facts must be carried over verbatim from the inspection rather than invented, which constrains how the nested facts object may be populated.

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 concrete artifacts: generates and saves business schema, website copy, and a business-profile description, from confirmed facts only. This clearly separates it from inspect_business_website (inspection), get_website_fixes (retrieval), and verify_website_fixes (verification).

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 an explicit sequencing rule: use after the user confirms the facts from inspect_business_website, and only with a connected account holding a paid or 7-day trial slot. It also states the precondition that the current revision must be passed, which effectively excludes stale-revision calls.

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