Skip to main content
Glama

Visibility Genies

Search Trustpilot businesses

search_trustpilot_businesses

Finds companies on Trustpilot by name or category, with rating, review count, and the domain that get_trustpilot_reviews takes. Usually completes within this call; a 'processing' response returns a taskId to call back with in 30-60 seconds at no extra cost. Estimated price: $0.01 for 10 results, billed per 10 at twice the Local page's normal-priority rate, so the call usually returns them. Each call may spend up to the workspace's agent spend limit ($2.00 unless changed in Settings) without asking: it holds at most its estimate plus a margin while it runs and is charged what it bought, never more. A call whose maximum is above the limit is refused before anything is bought, with its estimate and maximum: ask the user, then call again with approvedMaxCostUsd set to the amount they approved.

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": {
      "projectId": "<projectId>"
    },
    "name": "search_trustpilot_businesses"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoNumber of results to collect (10-140). Defaults to 10. Billed per 10 results.
taskIdNoResume a previous call that returned status "processing". Pass back the taskId exactly as returned (format "trustpilot_search:<id>"). Resuming charges no extra credits.
keywordNoCompany name or business category to find on Trustpilot. Required unless resuming with taskId.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
approvedMaxCostUsdNoThe most, in USD, the user approved for this call after seeing its estimate and maximum. Only needed after a call was refused for costing more than the workspace's agent spend limit; never set it without asking the user.

Output Schema

NameRequiredDescriptionDefault
costNo
metaNo
statusYes
taskIdYes
businessesNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: it discloses billing granularity ($0.01 per 10 results, billed at twice the Local page's normal-priority rate), the workspace agent spend limit and hold-and-charge semantics, the refusal-before-purchase flow, and the possibility of an asynchronous 'processing' state with a resumable taskId. This is exactly the context the readOnlyHint=false / openWorldHint=true annotations leave open, and it does not contradict them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is correctly front-loaded, but the pricing block is dense and partly circular ('Estimate: $0.01 for 10 results, billed per 10 at twice the Local page's normal-priority rate, so the call usually returns them'), repeating the per-10 billing already stated in the depth parameter and mixing pricing, timing, and spend-limit policy in one run-on stretch.

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?

With an output schema and a fully documented input schema, the description only needs to cover the non-structural behavior, and it does: cost, spend-limit approval, and async resumption. The only gap is the absence of any steer on when this source beats the sibling business-search tools.

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 already 100%, so the baseline is 3, but the description still adds practical meaning: it frames taskId as the resume path after a 'processing' response and clarifies that resuming costs nothing, and it constrains approvedMaxCostUsd to the post-refusal, user-approved case only. Depth and keyword semantics are essentially left to the schema.

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?

The opening sentence gives a specific verb and resource ('Finds companies on Trustpilot by name or category') and names the return fields, including the handoff detail that the domain is what get_trustpilot_reviews takes. It does not, however, distinguish itself from the other search siblings such as search_local_businesses or search_tripadvisor_businesses, so differentiation is only partial.

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?

There is real procedural guidance: what to do when a 'processing' response comes back (call again with the returned taskId in 30-60s at no extra cost) and what to do when a call is refused for exceeding the spend limit (ask the user, then retry with approvedMaxCostUsd). What is missing is when-to-use guidance against the alternative search tools or when Trustpilot is the right source versus local/TripAdvisor search.

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