Skip to main content
Glama
Sign In
Freelancer MCP Server

Freelancer MCP Server

by rodriguesvali
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Project Details

freelancer_get_project
Read-onlyIdempotent

Retrieve full details for a Freelancer.com project by ID, including budget, status, skills, bid stats, and timeline. Use it to review a project before bidding or responding.

Instructions

Get full details of a specific Freelancer.com project by ID.

Args:

  • project_id (number): The numeric project ID

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

Returns: full description, budget, status, skills, bid stats, timeline

Use when: "Tell me more about project 12345678", "Get the details for this project"

Input Schema

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

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=true and destructiveHint=false. The description adds value by specifying the returned fields (description, budget, status, etc.), providing context beyond the annotations.

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 concise with no wasted words; it front-loads the purpose and efficiently covers parameters, return content, and usage examples.

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?

For a simple get-by-id tool with 2 parameters and no output schema, the description covers purpose, parameters, return content, and usage examples. It omits error handling but is otherwise complete.

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%, and the description's 'Args' section mostly mirrors the schema descriptions. However, it adds a small extra by referencing freelancer_list_accounts for account labels.

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 'Get full details of a specific Freelancer.com project by ID', using a specific verb and resource, and it distinguishes from sibling tools like get_messages or search_projects by focusing on project details retrieval.

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?

It provides explicit usage examples like 'Tell me more about project 12345678' and explains when to use it, but does not explicitly state when not to use it or compare to alternatives such as freelancer_search_projects.

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