Skip to main content
Glama
Sign In
Freelancer MCP Server

Freelancer MCP Server

by rodriguesvali
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List My Projects

freelancer_my_projects
Read-onlyIdempotent

List projects you own or are hired on as a freelancer; filter by role and status, paginate results, and select the Freelancer account to query.

Instructions

List projects you own or are working on as a freelancer.

Args:

  • role (string): "owner" (projects you posted) or "freelancer" (projects you're hired on)

  • status (string, optional): "active", "complete", "closed"

  • limit (number, 1-50, default 10): Number of results

  • offset (number, default 0): Pagination offset

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

Returns: list of your projects with status, budget and progress. To analyze past performance ("what are my winning strategies?"), call this with status "complete" and pair it with freelancer_my_bids (status "awarded") — reason over the combined results yourself (skills used, budget ranges, proposal style).

Use when: "Show my active projects", "List projects I'm working on", "What projects have I posted?", "Analyze my past completed projects"

Input Schema

NameRequiredDescriptionDefault
roleNoowner = posted by you, freelancer = hired onfreelancer
limitNoNumber of results
offsetNoPagination offset
statusNoFilter by project status
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.6/5.0
Behavior4/5

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

Annotations already indicate readOnly, destructiveHint false, idempotent. The description adds that it returns a list with status, budget, and progress, and explains pagination via offset/limit. It doesn't discuss rate limits or data freshness, but the extra context is valuable.

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-organized: a one-sentence summary, then args in clear bullet-like format, then returns, then use-case. It is not overly verbose, though the return description could be slightly more concise. Still, every sentence adds value.

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?

Given no output schema, the description adequately covers return value structure (list with status, budget, progress). It also explains pagination and provides a sophisticated multi-tool usage scenario. For a list tool with good annotations, this is complete.

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 coverage is 100%, but the description adds value by explaining defaults (e.g., role default 'freelancer'), clarifying the account parameter's reference to another tool, and providing human-readable explanations for enums. This goes beyond the schema's brief field descriptions.

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 lists projects the user owns or is hired on. It distinguishes from siblings like 'freelancer_search_projects' which searches all projects, and 'freelancer_my_bids' which lists bids. The verb 'list' combined with 'your projects' specifies the resource and scope.

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

Usage Guidelines5/5

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

The description provides explicit usage examples ('Show my active projects', etc.) and includes guidance on when to use it for analysis, pairing with 'freelancer_my_bids'. It tells the agent to reason over combined results, which is a clear usage scenario.

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