Skip to main content
Glama
modelnorth

fiverr-phantom-mcp

by modelnorth

fiverr_add_skills

Bulk-add searchable skills to your Fiverr seller profile with chosen proficiency levels. Specify a list of skills and set each as Beginner, Intermediate, or Expert.

Instructions

Bulk-add search-indexed skills to the Fiverr seller profile. Levels: 'Beginner', 'Intermediate', 'Expert'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelNoExpert
skillsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of explaining behavior. It states that skills are bulk-added and search-indexed, but it does not disclose whether the operation replaces existing skills, is additive, requires authentication, or what side effects may occur.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, front-loads the core action, and includes the only necessary additional detail about levels. Every sentence carries useful information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the low complexity, an output schema, and only two parameters, the description is minimally adequate. However, it omits behavioral details such as whether existing skills are overwritten or appended, and it does not mention any usage prerequisites. These gaps matter for a mutation tool without annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It provides the allowed level values ('Beginner', 'Intermediate', 'Expert') and hints that skills are search-indexed, but the required 'skills' parameter receives no direct semantic explanation beyond its name and schema type.

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?

The description clearly identifies a specific verb and resource: 'Bulk-add search-indexed skills to the Fiverr seller profile.' It conveys a distinct action that is not easily confused with the sibling tool names, though it does not explicitly contrast itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided about when to use this tool versus alternatives such as fiverr_update_profile or fiverr_launch_login. The description gives no context on prerequisites, suitable scenarios, or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.