Skip to main content
Glama

Request sending review requests

request_send_review_requests
Destructive

Ask the user to approve sending review-request messages for one business by email or SMS (up to 25 recipients). Always needs approval (never runs under Always allow). Opted-out contacts are skipped and anyone contacted in the last 30 days is deferred. SMS uses one SMS credit per message part from the workspace balance. The message must contain the review link, or GBPly adds it at the end. For SMS you must confirm the business has the recipients' consent.

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": {
      "profile_id": "<profile_id>",
      "channel": "<channel>",
      "recipients": "<recipients>",
      "message": "<message>"
    },
    "name": "request_send_review_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYes
messageYes
previewNotrue = dry run: nothing is created, run, charged or sent to Google. Returns what would change, the credit cost and whether it would run straight away under Always allow. Use when the user wants to check first.
subjectNoEmail only.
profile_idYes
recipientsYesEmail addresses or phone numbers in international format (+44...).
consent_confirmedNoSMS only: the user confirmed recipients agreed to be contacted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly=false, destructive=true, openWorld=true, idempotent=false) by disclosing what actually happens: opt-out contacts are skipped, anyone contacted in the last 30 days is deferred, SMS consumes one credit per message part from the workspace balance, and the review link is auto-appended if missing. These are exactly the consequences an agent needs before invoking a destructive, credit-consuming send.

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?

Five tight sentences, front-loaded with the core action and limits, then consequences, then prerequisites. Slight redundancy in the trailing consent sentence, which largely restates the consent_confirmed schema description, keeps it from a 5.

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 destructive, credit-consuming, open-world tool with no output schema and 7 parameters, the description covers cost, deferral, opt-out, and consent well. It omits what the tool returns after approval (a pending request object? immediate send?) and does not mention the email-only subject field, leaving a modest gap for an approval-flow tool.

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 only 57%, and the description compensates by explaining the message-content constraint (must contain the review link) and the SMS consent prerequisite tied to consent_confirmed. It adds nothing for subject or preview, though preview is already well documented in the schema, leaving a small residual gap.

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 ('Ask the user to approve sending'), a specific resource ('review-request messages for one business'), and the channel/scale scope ('email or SMS, up to 25 recipients'). This distinguishes it cleanly from sibling reply/post/scan tools without needing to name them.

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 operating context: approval is always required (never runs under Always allow), SMS requires recipient consent confirmation, and the message must carry the review link. It does not name an alternative tool or an explicit when-not-to-use case, so it stops short of full routing guidance.

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