Skip to main content
Glama

Google Business Profile & Local SEO Checker

Triage a suspended or unverified profile

suspension_triage
Read-onlyIdempotent

For a suspended, disabled, unverified or limited Google Business Profile: ranks the likely causes from yes/no answers, says whether to appeal, re-verify or wait, and lists the evidence to gather plus a video verification shot list. Answer what you know and leave the rest out.

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": {
      "status": "<status>"
    },
    "name": "suspension_triage"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYesWhat Google shows: suspended, disabled, pending verification, limited, not showing
website_mismatchNoWebsite name/phone/area doesn't match the profile
multiple_profilesNoMore than one profile for the same business
po_box_or_mailboxNoAddress is a PO box or mailbox
recent_major_editsNoChanged name/address/category/phone recently
restricted_categoryNoLocksmith, garage door, towing, pest control, removalist or similar high-spam category
name_has_extra_wordsNoName has keywords, suburb or tagline not on signage
phone_not_local_or_trackingNoMain phone is a call centre, premium or tracking number
recently_moved_or_rebrandedNoMoved or rebranded recently
virtual_office_or_coworkingNoAddress is a virtual office, coworking or shared space
service_area_business_showing_addressNoGoes to customers but shows a street address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuine value by disclosing the shape of the response: ranked likely causes derived from yes/no inputs, an action recommendation, an evidence checklist, and a video verification shot list. It does not say how causes are ranked or how confident the recommendation is, but with no output schema it goes a long way.

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?

Scope first, deliverables second, input instruction last, with no filler. Both sentences carry information an agent needs to select and call the tool correctly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter, read-only diagnostic tool with no output schema, the description fully conveys what goes in, what comes out, and that partial input is acceptable. Only the ranking logic and result granularity remain undisclosed, which is a minor gap.

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% and each boolean already carries its own explanation, so the baseline is 3. The description adds only two things beyond the schema: that the flags are answered as yes/no signals feeding a ranking, and that unknown flags may be omitted. Useful, but marginal when every parameter is already documented.

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?

Names a precise verb set (ranks likely causes, recommends appeal/re-verify/wait, lists evidence and a shot list) against a specific resource state (suspended, disabled, unverified, limited GBP). This is clearly distinct from the sibling audit/check tools, which examine healthy profiles.

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?

The opening clause establishes exactly when to reach for it (profile in one of four bad states), and 'Answer what you know and leave the rest out' tells the agent how to behave with incomplete evidence. It stops short of naming an alternative for profiles that are merely under-optimised, but the applicability condition is unambiguous.

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.