Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fiverr_search

Search Fiverr public gig listings by keyword to return seller level, rating, reviews, starting price, category, and thumbnail for service comparison.

Instructions

Search Fiverr gigs. Searches Fiverr's public gig listings by free-text keyword, returning gig summaries (title, seller username, seller level, rating, review count, starting price, category, thumbnail image). Seller level uses the same values on the search, seller and gig endpoints: level_one_seller, level_two_seller, top_rated_seller, or new_seller.

Input Schema

NameRequiredDescriptionDefault
qYesFree-text gig search keyword
pageNo1-based result page. Defaults to 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 helpfully declares the data source is public gig listings (implying no auth) and, because no output schema exists, enumerates the returned fields — real behavioral value. However, it says nothing about pagination limits, total result caps, rate limits, or read-only/non-destructive guarantees beyond what 'search' implies, leaving gaps for a mutation-free but network-bound tool.

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?

Three sentences, front-loaded with purpose, then return shape, then the shared enum vocabulary. Every sentence carries information an agent would otherwise have to infer; 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 2-parameter read tool with no output schema and no annotations, the description supplies the missing return-field contract and explains the seller-level vocabulary an agent needs to interpret results. It falls just short of complete by omitting any statement about result volume, page depth limits, or behavior when no matches are found.

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 the schema already documents both q ('Free-text gig search keyword') and page ('1-based result page. Defaults to 1.'). The description's 'by free-text keyword' only restates the schema, and the seller-level enum note describes output values rather than any parameter. 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?

Starts with a specific verb+resource ('Search Fiverr gigs') and immediately scopes it to Fiverr's public gig listings by free-text keyword. The enumeration of returned fields (title, seller, rating, price, etc.) further pins down what this endpoint is versus the sibling detail endpoints fiverr_gig and fiverr_seller.

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: 'by free-text keyword' tells the agent this is keyword-driven lookup, and the note that seller level values are shared with the 'search, seller and gig endpoints' hints at the fiverr_seller/fiverr_gig relationship. There is no explicit when-to-use-this-instead-of-fiverr_gig or fiverr_seller statement, and no prerequisites or exclusions.

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