Search Fiverr gigs by keyword and return normalized listing summaries. Use fiverr_gig for one gig's details or fiverr_seller for the seller's profile.
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Free-text gig search keyword | |
| page | No | 1-based result page. Defaults to 1. |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | The tool result payload (shape varies per tool; see each tool's docs resource). |
Changes observed during successful MCP inspections.
Input schema / properties / page / descriptionAdded value: +"1-based result page. Defaults to 1."Input schema / properties / q / descriptionAdded value: +"Free-text gig search keyword"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety and open-web profile. The description adds that results are 'normalized listing summaries,' which is mild extra context, but it does not discuss result shape, ranking behavior, or pagination beyond what the schema states.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences with the core action front-loaded and the sibling routing second. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists and annotations cover safety, so the description needn't explain return values. For a 2-parameter search tool, the purpose plus explicit sibling routing makes the definition complete for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so q and page are already documented in the schema. The description only echoes 'by keyword,' adding no syntax, filtering, or format detail beyond the structured fields; baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (search) and resource (Fiverr gigs), plus what it returns (normalized listing summaries). It also names the two sibling tools (fiverr_gig, fiverr_seller) it is not, so an agent can distinguish it without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly routes the agent: use this tool for keyword gig search, use fiverr_gig for a single gig's details, and fiverr_seller for the seller's profile. The when-to-use-which is fully specified rather than inferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.