Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fiverr_search

Search Fiverr public gig listings by keyword and page, returning normalized summaries with title, seller level, rating, review count, starting price, category, and thumbnail.

Instructions

Search Fiverr gigs. Searches Fiverr's public gig listings by free-text keyword, returning normalized gig summaries (title, seller username, seller level, rating, review count, starting price, category, thumbnail image). Public data sourced from Fiverr's own server-rendered search pages via a real browser-rendering backend. 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

TableJSON 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.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It does disclose the data source (Fiverr's server-rendered search pages via a real browser-rendering backend), which hints at scraping behavior. It also explains seller level values. However, it does not mention rate limits, pagination behavior, or potential failures. The behavioral disclosure is partial but not misleading.

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?

The description is efficient: two sentences cover purpose and data source, plus a third clarifies seller level values. It is front-loaded with the core purpose and avoids unnecessary detail. The structure is clear and every sentence adds value.

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 search tool with no output schema, the description lists the returned fields (title, seller username, seller level, rating, review count, starting price, category, thumbnail), which is essential. It also explains the seller level enum. It does not detail pagination limits or error conditions, but for a straightforward search endpoint this is largely sufficient.

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% with both q and page described. The description adds that q is free-text and that page is 1-based (redundant with schema). It doesn't provide additional syntax or formatting guidance beyond the schema. Baseline 3 is appropriate since the schema already documents parameters.

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?

The description clearly states the tool searches Fiverr gigs by free-text keyword and returns normalized summaries. It differentiates from sibling tools like fiverr_gig (likely a specific gig lookup) and fiverr_seller (seller details) by focusing on search. The verb 'search' plus the resource 'Fiverr gigs' is specific and unambiguous.

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 description implies usage for keyword-based search but does not explicitly contrast with fiverr_gig or fiverr_seller. It lacks when-not-to-use guidance or mention of alternatives. The context that this returns summaries rather than full details is implied but not explicit, so an agent might not know when to prefer this over a direct gig fetch.

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