Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

capterra_search

Search Capterra products to find software options, returning product IDs, names, URLs, descriptions, and ratings for comparison.

Instructions

Search Capterra products. Returns Capterra search-result products (id, name, url, description, rating). Note: Capterra renders a fallback product list even for queries with no genuine match, rather than a distinct empty-results page, so callers should treat low-relevance results as an upstream characteristic, not a bug.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0
  2. Removedv1.6.0
  3. Addedv1.5.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it discloses a genuinely non-obvious upstream quirk: Capterra returns a fallback product list for no-match queries instead of an empty page, and callers should treat low-relevance hits as expected. It omits auth needs, rate limits, and pagination behavior, so it is not exhaustive.

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?

Two tight sentences: the purpose and return shape come first, then the single edge-case caveat. Every clause carries information an agent can act on, with no filler.

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 one-param search tool with no output schema and no annotations, the description covers purpose, result fields, and a critical result-quality caveat, which is close to complete. Missing pagination or result-count behavior keeps it just under a 5.

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?

One parameter at 100% schema description coverage ('q: Search query'), so the schema already documents the input fully. The description adds no syntax, formatting, or filtering detail beyond the schema, matching the baseline 3 for high-coverage single-param tools.

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?

States a specific verb and resource ('Search Capterra products') and enumerates the returned fields (id, name, url, description, rating), making the tool's scope unambiguous. It does not name or differentiate from the siblings capterra_product and capterra_reviews, so it falls short of a full 5.

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 implied by the verb 'Search' and the one required query param, but the description never states when to reach for this over capterra_product or capterra_reviews. The fallback-results note is a useful interpretation caveat rather than explicit when/when-not guidance.

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

Deploy Server

Other Tools