Skip to main content
Glama

MentionedOn Visibility and Website Fixes

Find your MentionedOn businesses

list_monitored_businesses
Read-onlyIdempotent

Needs a connected MentionedOn account. Start here: lists the businesses in the account with each one's id and monitoring status, or a setup link when there are none. Pass the id as businessId to the other tools. Read-only; starts no scan, trial or charge.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_monitored_businesses"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
nextStepYes
setupUrlYes
businessesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / businesses / items / properties / monitoring
      Added value: +{
      +  "enum": [
      +    "live",
      +    "paused",
      +    "plan_limit",
      +    "off",
      +    "payment_failed"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / businesses / items / required
      Previous value: -[
      -  "id",
      -  "name",
      -  "website",
      -  "active",
      -  "onboardingStatus"
      -]New value: +[
      +  "id",
      +  "name",
      +  "website",
      +  "active",
      +  "monitoring",
      +  "onboardingStatus"
      +]
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description goes further by ruling out side effects an agent might otherwise fear: 'starts no scan, trial or charge'. It also discloses the empty-state behavior (returns a setup link when there are no businesses), which is genuine behavioral context not present in 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.

Conciseness5/5

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

Three short sentences, front-loaded with the account prerequisite and the 'start here' directive before the return shape and safety note. No filler and no repetition of the title.

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 no-parameter, read-only entry-point tool with an output schema, the description covers prerequisite, return contents, empty case, and next-step usage. 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?

The tool takes zero parameters, so the baseline is 4; there is nothing to mis-specify. The description's note about passing the returned id as businessId to other tools adds useful cross-tool semantics even though it is about output rather than input.

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 ('lists the businesses in the account') plus what each entry carries (id, monitoring status). The 'Start here' framing and the instruction to pass the id as businessId to other tools make it unmistakably distinct from the visibility/article siblings.

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?

Gives a clear entry-point condition ('Start here') and a prerequisite ('Needs a connected MentionedOn account'), and explains the downstream handoff to the other tools. It does not name any alternative or when-not case, but for a first-call discovery tool there is little competing option to disambiguate.

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