Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fiverr_gig

Fetch a Fiverr gig's full details—title, pricing tiers, ratings, reviews, tags, gallery, and seller summary—using the seller username and gig slug.

Instructions

Get Fiverr gig detail. Returns a normalized Fiverr gig detail page: title, description, category, pricing packages (basic/standard/premium tiers with price and delivery time), rating, review count, orders in queue, tags, gallery images, and a seller summary (level, rating, response time, languages). Public data sourced from Fiverr's own server-rendered gig 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
slugYesFiverr gig URL slug, the trailing path segment after the username in a gig URL
usernameYesFiverr seller username, e.g. from a search result's seller_username field

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?

With no annotations, the description carries the full burden. It does disclose meaningful behavioral context: data is public, sourced from server-rendered pages via a real browser-rendering backend (implying slower retrieval), and normalized. It also clarifies cross-endpoint consistency of seller-level values. However, it does not address failure modes, rate limits, or freshness, so it is adequate but not rich.

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 core purpose is front-loaded in the first sentence, followed by a compact list of return fields and a source-provenance note. The trailing clarification about seller-level enum values is slightly verbose but earn its place by preventing misinterpretation; no filler is present.

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 two-parameter read-only lookup with no output schema, the description covers the returned content, data provenance, and parameter sourcing context (schema covers URL derivation). Everything an agent needs to call it correctly is present; only deeper response details like error handling are absent, which is minor for this complexity.

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 baseline of 3 applies. The tool description adds no new parameter meaning beyond the schema's definitions of 'slug' and 'username', both of which are already well documented in the input schema.

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 opens with a specific verb and resource ('Get Fiverr gig detail') and enumerates the complete set of returned fields (title, category, pricing tiers, rating, etc.), leaving no ambiguity about what the tool does. It is clearly distinguishable from sibling tools fiverr_search and fiverr_seller by targeting the gig detail page specifically.

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 verb phrase 'Get Fiverr gig detail' implies the use case: fetch a gig when you have its username and slug. However, there is no explicit statement about when to prefer this over fiverr_search or fiverr_seller, nor any exclusions or routing guidance. Usage context is clear but alternatives are left to inference rather than named.

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