Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fiverr_seller

Retrieve a Fiverr seller's public profile by username to get normalized details such as seller level, country, languages, hourly rate, join date, and gig IDs.

Instructions

Get Fiverr seller profile. Returns a normalized Fiverr seller profile: display name, one-liner title, description, country, seller level, verification status, hourly rate, spoken languages, join date, and the seller's gig ids. Public data sourced from Fiverr's own server-rendered seller profile 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
usernameYesFiverr seller username, e.g. from a search result's seller_username field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It adds valuable context: data is public, sourced from server-rendered profile pages via a real browser-rendering backend, normalized, and seller level values are consistent across endpoints. It does not disclose rate limits, failure modes, or latency implications of browser rendering, which keeps it from a 5.

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?

Four sentences, each earning its place: purpose, return fields, data source, and seller-level enum values. The field enumeration is slightly long but justified because there is no output schema. Overall compact and front-loaded with the purpose.

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 one-parameter, public-data profile tool, the description is complete: it states what the tool returns, where the data comes from, the domain of seller level values, and the input source. It lacks only edge-case behavior (e.g., nonexistent usernames) and an explicit read-only confirmation, which are minor given the simple scope.

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% and the username parameter is well-described, including where to obtain it. The description adds no extra parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.

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 ('Get Fiverr seller profile') and enumerates the returned fields (display name, seller level, gig ids, etc.). This clearly distinguishes it from sibling tools like fiverr_gig (gig details) and fiverr_search (search), so an agent can identify the right tool without opening its 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 intended usage is clear: retrieve a single seller profile when you have a Fiverr username. The schema parameter description even hints at a workflow ('from a search result's seller_username field'). However, the description does not explicitly mention alternatives or exclusions, such as 'use fiverr_search to find sellers' or 'use fiverr_gig for gig details,' leaving a small amount of inference.

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