Skip to main content
Glama

Google Business Profile & Local SEO Checker

Build a direct review link + QR code

build_review_link
Read-onlyIdempotent

Turns a Google Place ID into a direct 'write a review' link that opens the review box, plus a printable QR code image. Catches the common mistake of using a CID or Maps ID instead of a Place ID.

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": {
      "place_id": "<place_id>"
    },
    "name": "build_review_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
place_idYesGoogle Place ID (usually starts with ChIJ). Find it with Google's Place ID finder
business_nameNoOptional, for labelling

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description still adds real value by disclosing what is produced (a link that opens the review box directly, plus a printable QR image) and by flagging the common CID/Maps ID failure mode. It stops short of saying what happens on an invalid ID or what format the QR image is returned in.

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?

Two tight sentences with no filler, and the primary capability is front-loaded before the caveat. Structure is clean; the caveat sentence could name what to do if you only have a CID, but the economy is appropriate.

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 read-only two-parameter tool with no output schema, the description covers what it consumes and what it produces, and annotations cover safety. The remaining gap is the return shape (how the link and QR image are delivered, e.g. URL string vs base64 image), which an agent may need before wiring up a response.

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 the schema already documents both parameters including the 'usually starts with ChIJ' hint and the 'optional, for labelling' note. The description's only addition is negative guidance that a CID or Maps ID is the wrong value, which sharpens the meaning of place_id but is already partly implied by the schema. Baseline 3 fits.

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 transformation: 'Turns a Google Place ID into a direct write-a-review link ... plus a printable QR code image.' Verb and resource are unambiguous and the scope (link plus QR) is concrete; the only gap is that it never contrasts itself with the sibling check/audit tools, though none of them plausibly overlap.

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?

Usage is implied by the purpose rather than stated: an agent can infer you call this when you need a review-collection link, but there is no explicit when-to-use or when-not-to-use sentence and no reference to any alternative tool. The CID/Maps ID warning is an input caveat, not usage routing.

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