Skip to main content
Glama
Sign In
Freelancer MCP Server

Freelancer MCP Server

by rodriguesvali
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update Specialty Profile

freelancer_update_profile
Idempotent

Update fields on a Freelancer.com specialty profile, including tagline, hourly rate, description, or skills. Change only the fields you supply; this does not edit your main account profile.

Instructions

Update fields on one of your Freelancer.com "specialty profiles". Only the fields you supply are changed.

Important: this edits a SPECIALTY profile identified by profile_id — it does NOT edit your main account profile (description/tagline/hourly rate shown on your public freelancer page). Freelancer's public API exposes no endpoint to edit the main profile; that is web-UI-only.

Args:

  • profile_id (number): The specialty profile's numeric ID (you must already know it)

  • tagline (string, optional)

  • hourly_rate (number, optional): USD

  • description (string, optional)

  • skills (string[], optional): Skill names or IDs (replaces this profile's skills)

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

Returns: confirmation.

⚠️ Modifies real data. The API enforces ownership: editing a profile_id you don't own is rejected.

Use when: "Update specialty profile 12345's hourly rate to 40"

Input Schema

NameRequiredDescriptionDefault
skillsNoSkill names or IDs (replaces profile skills)
accountNoWhich configured Freelancer account to use (see freelancer_list_accounts for labels). Omit to use your default/only account.
taglineNoShort headline
profile_idYesSpecialty profile numeric ID
descriptionNoProfile description
hourly_rateNoHourly rate in USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate the tool is non-read-only, idempotent, and non-destructive. The description adds that it modifies real data, the API enforces ownership, and only supplied fields are changed. This provides additional behavioral context beyond annotations.

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?

The description is well-structured with a clear statement, an important note, a parameter list, behavioral notes, and a usage example. Each part contributes value, though it could be slightly more concise.

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?

Given the tool has 6 parameters and no output schema, the description covers the use case, prerequisites, ownership enforcement, and partial update behavior. It lacks details on error handling or synchronous/asynchronous behavior, but is largely complete for a mutation tool.

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

Parameters4/5

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

Schema description coverage is 100%, but the description adds extra meaning: hourly_rate is in USD, skills replaces the profile's skills, and account refers to freelancer_list_accounts. This goes beyond the schema descriptions, making parameters clearer for the agent.

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?

The description clearly states the tool updates fields on a specialty profile and explicitly distinguishes it from the main account profile, which is web-UI-only. It specifies the resource (specialty profile) and the action (update), and differentiates from sibling tools like freelancer_create_profile.

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 description provides a usage example ('Use when: Update specialty profile 12345's hourly rate to 40'), states the prerequisite of knowing the profile_id, and explains that the account parameter can be omitted. It notes that this tool does not edit the main profile, but does not explicitly mention alternatives for skills management or other profile operations.

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