Skip to main content
Glama

Google Business Profile & Local SEO Checker

Check a GBP description

check_gbp_description
Read-onlyIdempotent

Checks a Google Business Profile description before it's saved: the 750-character limit, links, prices or promotions (not allowed), keyword stuffing, AI-style filler, missing area or services, and what shows before 'More'. Gives a four-block structure that works.

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": {
      "description": "<description>"
    },
    "name": "check_gbp_description"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional: main city or suburb
servicesNoOptional: main services that should be mentioned
descriptionYesThe description text
business_nameNoOptional

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety needs no restating. The description adds the substantive behavior – the specific rule set applied and that it returns a 'four-block structure that works' – but says nothing about how results are reported (pass/fail vs. suggestions) or the shape of the response, which matters since no output schema exists.

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 verb and resource, then a dense but efficient enumeration of checks, closing with the value proposition. The check list is long but each item earns its place; no filler sentences.

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 single-input read-only checker with no output schema, the definition covers what is validated and hints at the returned structure, which is enough for an agent to select and call it. It is slightly thin on what the response actually contains and on how optional params change the verdict.

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 all four parameters are already documented, and the description only glancingly touches parameter meaning via 'missing area or services' – which maps to the city/services inputs already described in the schema as 'main services that should be mentioned'. It adds inference value but no real syntax or format detail beyond the schema.

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 specific verb and resource ('Checks a Google Business Profile description') and enumerates exactly what is validated: the 750-character limit, links, prices/promotions, keyword stuffing, AI filler, missing area/services, and the pre-'More' truncation. This is clearly distinguishable from siblings like check_gbp_post or audit_gbp_profile 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'before it's saved' gives a clear use context (pre-publication validation), which is genuinely actionable. It stops short of any when-not guidance or naming an alternative tool, but the timing guidance 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.