Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (96 Tools)

trustpilot_business_reviews_rating_scraper

Read-onlyIdempotent

Trustpilot Business Reviews & TrustScore Scraper ($1/1k): Real-time structured data extraction feed for Trustpilot Business Reviews & TrustScore Scraper ($1/1k).

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

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum number of records to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so safety and idempotency are covered structurally. The description does add one piece of genuinely non-schema information — the "$1/1k" cost model — which is useful for budgeting, but it says nothing about rate limits, freshness semantics despite the "real-time" claim, or what happens on unscrapable targets.

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?

It is a single short sentence and the platform name is front-loaded, so it is not bloated in length. But roughly half the sentence is a verbatim repetition of the title after the colon, and "real-time structured data extraction feed for" is filler that does not earn its place.

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?

Reassessing against the actual structured payload: with annotations covering the safety/idempotency profile, a 100%-covered single parameter, no output schema, and no nested objects, the remaining burden on the description is modest and largely discharged by the platform-and-resource identification plus the cost note. The main residual gap is freshness/rate behavior for a "real-time" feed, which is a real but bounded omission rather than a crippling one.

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?

Only one parameter exists (maxResults) with 100% schema description coverage ("Maximum number of records to return."), so the schema carries the parameter burden fully. The description adds no meaning beyond that, which is the baseline case rather than a failure.

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

Purpose3/5

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

The name and description identify a specific resource (Trustpilot Business Reviews & TrustScore) and the action (scraping/extraction), which does distinguish it from the G2/Capterra and Amazon review scrapers by platform. However, the body text is a near-tautological restatement of the title ("Trustpilot Business Reviews & TrustScore Scraper") wrapped in generic marketing phrasing ("real-time structured data extraction feed"), so the agent learns nothing about what is actually returned beyond the platform name.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no statement of what inputs identify a target business, no exclusions, and no pointer to sibling review scrapers even though several exist (e.g. g2_capterra_software_reviews_scraper). The only signal an agent has is the platform name in the title.

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