Skip to main content
Glama

Google Business Profile & Local SEO Checker

GBP optimisation checklist

optimisation_checklist
Read-onlyIdempotent

Returns the full step-by-step Google Business Profile optimisation checklist an agency works through (categories, name, description, contact links, service area, hours, attributes, services, products, photos, reviews, posts, booking, website and citations), tailored to the trade and city.

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": "optimisation_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoe.g. Melbourne
business_typeNoe.g. electrician, hair salon
service_area_businessNoTrue if they go to the customer (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety and determinism are covered. The description adds that output is a full enumerated checklist tailored by trade and city, but says nothing about format, length, or how tailoring changes the content beyond recency of detail.

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?

A single sentence, front-loaded with the return value and followed by the tailoring clause. The long parenthetical enumeration is dense but each item earns its place by telling the agent what topics the checklist covers.

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

Completeness3/5

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

With no output schema, the description must carry return-value expectations; it lists topics but not the structure (numbered steps? prose? markdown?). All three parameters are optional and the description never states what happens with zero arguments, which is a real gap for a read tool an agent may call bare.

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%, so all three parameters are already documented with examples. The description only reinforces that the result is tailored to trade and city and does not explain service_area_business, so it adds little beyond the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: returns the full step-by-step GBP optimisation checklist, and enumerates the checklist areas (categories, hours, photos, reviews, posts, etc.) plus the tailoring dimensions (trade, city). This is far from tautological, but it does not name or contrast itself with siblings such as audit_gbp_profile, leaving the checklist-vs-audit distinction to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The phrase 'an agency works through' implies this is a reference/worklist artifact rather than a diagnostic audit, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent facing audit_gbp_profile and this tool gets only an indirect signal about which to pick.

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