Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

G2 & Capterra Software Reviews, Ratings & Buyer Intent

scrape_g2_capterra_software_reviews
Read-onlyIdempotent

Extract SaaS star ratings, review counts, G2 and Capterra listing URLs, pricing pages, free-trial flags, and verified vendor emails to compare software and enrich B2B lead lists.

Instructions

Extract SaaS product star ratings, review counts, G2 & Capterra listing URLs, pricing pages, free-trial flags, and verified vendor contact emails ($0.80/1k).

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": {
      "queries": "<queries>"
    },
    "name": "scrape_g2_capterra_software_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
queriesYesSoftware product names or SaaS categories, e.g. ["Calendly", "Pipedrive", "Intercom"]
maxItemsNoMaximum SaaS review records

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds value annotations do not carry: a per-record cost model ($0.80/1k) and the fact that verified vendor emails are among the outputs. It still omits pagination/truncation behavior and how cost scales with the queries array.

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

Conciseness5/5

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

A single dense sentence front-loads the verb and the highest-value outputs, with the cost disclosure appended last. Every clause names a distinct return field; there is no filler or repetition of the title.

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 no output schema, the field enumeration in the description partially substitutes for one, and annotations cover the safety and openness profile. What remains thin is record structure and coverage guarantees (e.g., whether emails are always present, how many results per query). For a two-parameter read-only scraper this is close to sufficient.

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 description coverage is 100%, with both queries and maxItems documented including an example array and a default of 15, so the schema does the heavy lifting. The description adds no meaning about how multiple queries are batched, whether maxItems applies per query or in total, or what happens with ambiguous product names. Baseline 3 is appropriate.

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?

"Extract SaaS product star ratings, review counts, G2 & Capterra listing URLs..." gives a specific verb (extract) plus a clearly bounded resource (software review data from two named sources), and enumerates the concrete fields returned. An agent can distinguish this from generic lead-scraper siblings by the source-specific scope. It stops short of naming a sibling it is not, so it falls just below the top mark.

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 only implied: the source and field list make it obvious this is for pulling SaaS review/rating intelligence, but there is no explicit when-to-use, when-not-to-use, or pointer to adjacent tools like extract_saas_competitor_pricing_matrix. No prerequisites, input limits, or caveats about coverage are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.