Skip to main content
Glama

Google Business Profile & Local SEO Checker

Pre-flight a GBP post

check_gbp_post
Read-onlyIdempotent

Checks a Google Business Profile post before publishing so it doesn't get rejected: phone numbers in the text (a top cause of silent rejections), link shorteners, contact details, all caps, gimmicky punctuation, regulated products, length. Returns fixes and a three-line post format that publishes reliably.

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": {
      "text": "<text>"
    },
    "name": "check_gbp_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe post text
buttonNoOptional: the button type planned, e.g. 'Learn more', 'Call now', 'Book'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds value beyond them by explaining that rejections can be silent and by disclosing what comes back ('fixes and a three-line post format'). It does not mention auth, quotas, or what a pass/fail verdict looks like.

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?

Front-loaded with the purpose, then a tight enumerated list of checks, then the return value. The parenthetical 'a top cause of silent rejections' is justified motivation; the sentence is dense but each clause earns its place.

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 a two-parameter read-only checker with no output schema, the description supplies the important missing piece — that it returns fixes and a reliable post format. Only the shape of the fix output and any rate limits remain unspecified.

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 both parameters are already documented. The description implies the text parameter carries the phone numbers, link shorteners, and length being checked, but says nothing about how the optional 'button' value affects the check.

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 ('Checks a Google Business Profile post before publishing') and enumerates the exact failure modes it screens for, which clearly differentiates it from siblings like check_gbp_description and check_review_reply.

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 trigger ('before publishing') so an agent knows the right moment to call it, but never names an alternative tool or states when-not to use it.

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.