Skip to main content
Glama

Reviews: who to ask for a Google review (recent customers from the CRM)

review_request_candidates
Read-onlyIdempotent

Who to ask for a Google review: the client's recent customers from its connected CRM (won opportunities and kept appointments in the last days), with the channel to use (text when there's a phone, else email). Leaves out anyone asked in the last 90 days, anyone on do-not-disturb, anyone with no phone or email, and anyone whose full name already appears on a review. Returns the Business Profile review link and the default message. Read-only. Offer it when reviews are the client's lever (few reviews against the map competitors). Then review_request_send.

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": {
      "client": "<client>"
    },
    "name": "review_request_candidates"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNohow far back to look for customers
clientYesClient name from list_clients

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (which already cover read-only/idempotent/non-destructive): it discloses the filtering logic (last 90 days, DND, no contact info, name already on a review), the channel-selection rule (text if phone else email), and the return payload (review link + default message). This is rich, non-redundant behavioral context.

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 identity and purpose, then filtering rules, return values, and guidance in a logical order. Dense but each clause carries real information; the multiple exclusion rules make it slightly long, but nothing is clearly wasteful.

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

Completeness5/5

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

For a read-only 2-param tool with no output schema, it fully covers what matters: filtering criteria, channel logic, and the return contents. Nothing an agent needs to call it correctly or to decide follow-up is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so baseline is 3, but the description adds meaning to `days` by clarifying it scopes 'won opportunities and kept appointments' rather than arbitrary activity. Reasonable added semantics over the schema's terse 'how far back to look'.

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 resource (candidate customers to ask for a Google review) with its source (connected CRM), and distinguishes itself from sibling review_request_send by naming it as the downstream step. An agent can identify this as the 'picking' stage of review outreach 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?

Gives clear trigger context ('Offer it when reviews are the client's lever (few reviews against the map competitors)') and routes to the next tool ('Then review_request_send'). Usage condition is clear, though it doesn't state explicit 'do not use when' exclusions or differentiate from review_request_status.

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.