Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fiverr_gig

Retrieve complete Fiverr gig details using seller username and gig URL slug, including pricing tiers, delivery times, ratings, reviews, tags, gallery, and seller profile.

Instructions

Get Fiverr gig detail. Returns a 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). 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
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
Behavior4/5

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

With no annotations, the description carries the full behavioral burden, and it does well by enumerating what the call returns (packages, rating, review count, orders in queue, gallery, seller summary). It omits failure/error behavior and any rate-limit or auth notes, but for a read-only detail endpoint the return-shape disclosure is the meaningful part.

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 core action, followed by a return-field list and a shared-enum note. The enumerated fields are long but each earns its place since there is no output schema; minor trimming possible but generally efficient.

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 justifiably details the returned fields, and both required params are covered by the schema. It lacks any note on error conditions or resolution rules (e.g. gig not found), but is otherwise sufficient for calling the tool correctly.

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 'username' and 'slug' are already documented with format hints in the schema. The description adds nothing about parameter syntax beyond the schema baseline, so a 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?

States a specific verb+resource ('Get Fiverr gig detail') and clarifies it returns a full gig detail page. It distinguishes itself from the sibling fiverr_search/fiverr_seller by being the detail-level endpoint, though it never explicitly names those siblings as alternatives to route between.

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 the 'gig detail' framing; there is no explicit when-to-use guidance and no statement of alternatives (e.g. use fiverr_search to find and fiverr_gig to resolve a specific gig). The reference to the shared seller-level enum across 'search, seller and gig endpoints' hints at the sibling relationship but does not direct tool selection.

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