Skip to main content
Glama

MentionedOn Visibility and Website Fixes

Read saved website fixes

get_website_fixes
Read-onlyIdempotent

Needs a connected MentionedOn account. Use after inspect_business_website to see the current revision of saved facts, schema and copy, and whether each fix is installed. Needs businessId from list_monitored_businesses. Read-only; returns the revision number you must pass to draft_website_fixes (and to inspect_business_website and verify_website_fixes).

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_website_fixes"
  }
}

Input Schema

NameRequiredDescriptionDefault
businessIdYesBusiness id returned by list_monitored_businesses.

Output Schema

NameRequiredDescriptionDefault
recordYes
nextStepYes
businessIdYes
limitationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the bare 'Read-only' clause adds little. What does add value is the account prerequisite ('Needs a connected MentionedOn account') and the pipeline obligation around the returned revision, which are behavioral facts the annotations cannot express. It stops short of noting anything about staleness or failure modes when no fixes are saved.

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?

Three sentences, all load-bearing, covering prerequisite, purpose, and hand-off with no filler. Minor deduction: the purpose clause sits after the account prerequisite, so the agent reads an environment requirement before learning what the tool actually returns. Leading with 'Returns the current revision...' would front-load better.

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 single-parameter read tool with an output schema and full annotation coverage, the description supplies everything else the agent needs: account prerequisite, upstream tool for the id, prior-step ordering, and where the revision number is consumed. Return-value detail is correctly left to the output schema.

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?

With one parameter at 100% schema description coverage, the schema already documents businessId as the id returned by list_monitored_businesses. The description restates that same provenance rather than adding a new constraint or format detail. Baseline 3 applies because the schema is carrying this dimension.

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 and resource: shows 'the current revision of saved facts, schema and copy, and whether each fix is installed.' That distinguishes it cleanly from draft_website_fixes (writing), verify_website_fixes (checking installed state), and inspect_business_website (the prior inspection step). An agent can pick it out of the sibling list without opening any schema.

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?

It gives explicit sequencing ('Use after inspect_business_website'), names the source of the required id ('Needs businessId from list_monitored_businesses'), and states the downstream contract (the revision number must be passed to draft_website_fixes). That is when-to-use, prerequisites, and hand-off in one place, with nothing left to inference.

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