Skip to main content
Glama
Sign In
Freelancer MCP Server

Freelancer MCP Server

by rodriguesvali
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get My Profile

freelancer_get_self
Read-onlyIdempotent

Retrieve your own Freelancer.com profile to check reputation, earnings, skills, location, hourly rate, and stats for a selected or default account.

Instructions

Retrieve your own Freelancer.com profile, including reputation, earnings, skills, location and stats.

Args:

  • account (string, optional): Which configured Freelancer account to use (see freelancer_list_accounts for labels). Omit to use your default/only account.

Returns:

  • username, display name, tagline, location

  • reputation score and total reviews

  • registered skills/job categories

  • hourly rate and earnings

  • registration date

Use when: "What's my profile?", "Show my reputation", "What are my stats on Freelancer?"

Input Schema

NameRequiredDescriptionDefault
accountNoWhich configured Freelancer account to use (see freelancer_list_accounts for labels). Omit to use your default/only account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint, idempotentHint, destructiveHint=false. Description adds detail on what fields are returned (reputation, earnings, etc.), exceeding the minimal annotation coverage.

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?

Description is front-loaded with the main purpose and includes a useful Returns section. The Args block is somewhat redundant with the schema, but overall it remains concise and well-organized.

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

Completeness5/5

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

Despite no output schema, the description thoroughly explains return values (username, location, etc.) and provides usage examples. It is fully adequate for a simple read-only tool with good annotations.

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% for the single optional parameter. The description's Args block mostly duplicates the schema, adding no new semantic value beyond what is already documented.

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?

Clearly states 'Retrieve your own Freelancer.com profile' with specific verb and resource. Distinguishes from sibling tools like freelancer_get_user (other user) and freelancer_update_profile (modify).

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?

Provides explicit usage examples like 'What's my profile?' in the 'Use when' section, giving clear context. However, it does not explicitly state when not to use or mention alternatives.

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