Skip to main content
Glama

Capterra category products

run_capterra_category_products
Read-onlyIdempotent

List Capterra products within a software category, ranked as Capterra ranks them. 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": {
      "category": "<category>"
    },
    "name": "run_capterra_category_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYesCategory alias or URL. e.g. customer-relationship-management-software
max_itemsNoMax items (up to 500) Default: 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Capterra category alias or URL, e.g. customer-relationship-management-software (see run_capterra_categories)."New value: +"Category alias or URL. e.g. customer-relationship-management-software"
    • changedInput schema / properties / max_items / description
      Previous value: -"Maximum number of products to return (1-500, default 25). Billed at 1 point per returned record."New value: +"Max items (up to 500) Default: 10."
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description adds genuinely new behavioral context beyond the schema and annotations: results are returned in Capterra's ranking order, and each returned record costs 1 point (a credit/cost disclosure). It omits pagination behavior, but the ranking and cost notes are real value-adds.

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 short sentences, both front-loaded with the key facts (what it lists and how results are ordered, then the cost). Every clause earns its place 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?

There is no output schema, so the description carries the return-shape burden, and it does state that a ranked list of products comes back. Combined with full schema coverage and rich annotations, this is nearly complete; only pagination/response-detail specifics are absent.

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 the category (alias or URL) and max_items (up to 500, default 10) are fully documented in the schema. The description adds no further parameter syntax or format detail, so the baseline of 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?

The description gives a specific verb (List), resource (Capterra products), and scope (within a software category), which cleanly separates it from run_capterra_product (single) and run_capterra_products_search. It also states the ordering is Capterra's own ranking, a distinguishing trait. It does not explicitly name the sibling alternatives, keeping it just short of a 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?

The phrase 'within a software category' implies you invoke this when you already have a category alias/URL, so usage is inferable. However, there is no explicit when-to-use vs. when-not, no guidance on how this differs from run_capterra_products_search or run_capterra_categories, and no prerequisites stated.

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