Skip to main content
Glama

Capterra products search

run_capterra_products_search
Read-onlyIdempotent

Search Capterra software products by keyword: name, rating, review count, and image. 1 point per returned record.

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": {
      "query": "<query>"
    },
    "name": "run_capterra_products_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch term. e.g. crm software
max_itemsNoMax items (up to 250) Default: 25.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / max_items / description
      Previous value: -"Maximum number of products to return (1-250, default 25). Billed at 1 point per returned record."New value: +"Max items (up to 250) Default: 25."
    • changedInput schema / properties / query / description
      Previous value: -"Search term, e.g. 'crm software'."New value: +"Search term. e.g. crm software"
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-schema behavior: '1 point per returned record', a billing/cost characteristic that directly affects how an agent sizes max_items. It stops short of describing pagination or result ordering.

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, zero filler, with the core action front-loaded and the cost note appended where it is most relevant. Nothing repeats the schema needlessly.

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 description usefully enumerates the returned fields and notes the per-record cost, which is enough to call the tool correctly. The remaining gap is routing guidance among the Capterra siblings, which is a usage rather than completeness concern.

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%, so both query and max_items (with its 1-250 range and 25 default) are already documented in structured form. The description only restates that the search is keyword-based, adding no syntax, matching, or ranking semantics. Baseline 3 applies.

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 description names a specific verb and resource ('Search Capterra software products by keyword') and even previews returned fields (name, rating, review count, image). It does not, however, differentiate itself from close siblings like run_capterra_category_products or run_capterra_product, so an agent must infer the boundary.

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 explicit when-to-use guidance or mention of alternatives, despite three closely related Capterra siblings (categories, category_products, product, products_reviews). The word 'keyword' implies free-text search, but the agent is left to guess that run_capterra_category_products is the browse-by-category path.

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