Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fiverr_seller

Get a Fiverr seller profile by username to view level, verification, hourly rate, languages, join date, and gig IDs.

Instructions

Get Fiverr seller profile. Returns a 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. 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
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.5/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 the burden. It discloses the returned fields and even enumerates the seller_level values, which is genuinely useful, but it says nothing about permissions, rate limits, or pagination. 'Get' implies a safe read but that is left to inference.

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 action, then a compact enumeration of return fields. The seller_level enum sentence is long but earns its place by preventing value confusion across endpoints. No filler sentences.

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?

With no output schema, the description compensates by listing what is returned, including the seller_level value space. For a one-parameter, low-complexity lookup tool this is close to complete, though it omits confirmations like read-only status or how gig ids should be used downstream.

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% for the single username parameter, so the schema already does the documenting. The description's enum detail applies to the returned seller_level, not to an input, so it adds little parameter-level meaning. Baseline 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 and resource ('Get Fiverr seller profile') that clearly distinguishes it from fiverr_gig and fiverr_search siblings. Could be sharper about the fact that it takes a username rather than an id, but the core purpose is 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?

Usage is implied: fetch a seller profile given a username sourced from a search result. There is no explicit when-to-use vs fiverr_search or fiverr_gig, and no stated prerequisites or exclusions, so it sits at the minimum-viable level.

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