Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

trustmrr_startups

List all TrustMRR startups with pagination to enumerate the directory. Get each startup slug for fetching full verified profiles.

Instructions

List all TrustMRR startups. Returns a paginated list of every startup in the TrustMRR directory. Each entry is a slug you can pass to /trustmrr/startup/{slug} for the full verified profile — together these two endpoints let you enumerate the entire directory.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number (default 1)
page_sizeNoItems per page (default 100, max 1000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the return is a paginated list of slugs rather than full profiles, which shapes downstream calls. However, it says nothing about authentication, rate limits, or directory size, so behavioral context is only partially covered.

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

Conciseness4/5

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

Front-loaded with the verb+resource, and every sentence is short. There is mild redundancy between 'List all TrustMRR startups' and 'every startup in the TrustMRR directory,' but overall it is efficient and readable.

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?

No output schema exists, so the description must explain return values — it does, describing a paginated list of slugs and how to use them. Combined with the fully documented params, an agent has what it needs to call and chain the tool, though volume/auth details 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 coverage is 100%, so the schema already documents page and page_size with defaults and max. The description only restates that the response is paginated and adds no new meaning on parameter usage. Baseline 3 is correct.

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

Purpose5/5

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

States a specific verb and resource ('List all TrustMRR startups') and distinguishes itself from the sibling trustmrr_startup by explaining that this endpoint returns slugs which feed into the detail endpoint. An agent can tell it apart from trustmrr_startup without opening either schema.

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

Usage Guidelines4/5

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

The closing clause frames the tool's role: use this to enumerate the directory, then feed each slug to /trustmrr/startup/{slug} for the full profile. That routing context is clear, but there are no explicit exclusions (e.g., 'use trustmrr_search when you already know the name').

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