Skip to main content
Glama
fieldjoshua

Upwork MCP Server

by fieldjoshua
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search Upwork Jobs

upwork_search_jobs
Read-onlyIdempotent

Search Upwork freelance jobs using filters like skills, budget, job type, and experience level. Find matching opportunities with client details and posting dates.

Instructions

Search for freelance jobs on Upwork with various filters.

This tool searches the Upwork job marketplace and returns matching job listings. Use it to find opportunities based on skills, budget, category, and more.

Args:

  • query (string, optional): Search keywords for job titles/descriptions

  • category (string, optional): Job category filter

  • skills (string[], optional): Filter by required skills

  • budget_min (number, optional): Minimum budget in USD

  • budget_max (number, optional): Maximum budget in USD

  • job_type ('hourly' | 'fixed', optional): Filter by job type

  • experience_level ('entry' | 'intermediate' | 'expert', optional): Filter by level

  • client_country (string, optional): Filter by client's country

  • posted_within_hours (number, optional): Jobs posted within N hours

  • payment_verified (boolean, optional): Only verified payment methods

  • limit (number): Max results (default: 20, max: 100)

  • offset (number): Pagination offset (default: 0)

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: List of matching jobs with details including title, budget, skills, client info, and posting date.

Examples:

  • Find React jobs: query="react developer", skills=["react", "javascript"]

  • High-budget fixed jobs: job_type="fixed", budget_min=1000

  • Recent expert jobs: experience_level="expert", posted_within_hours=24

Error Handling:

  • Returns "No jobs found" if search returns empty

  • Returns error message if authentication fails

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of jobs to return (default: 20, max: 100)
queryNoSearch keywords to match against job titles and descriptions
offsetNoNumber of results to skip for pagination
skillsNoFilter by required skills (e.g., ['python', 'react', 'nodejs'])
categoryNoJob category filter. Common categories: web-development, mobile-development, software-development, data-science-analytics, design-creative, etc.
job_typeNoFilter by job type: 'hourly' or 'fixed'
budget_maxNoMaximum budget in USD
budget_minNoMinimum budget in USD
client_countryNoFilter by client's country (e.g., 'United States', 'United Kingdom')
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
experience_levelNoFilter by experience level: 'entry', 'intermediate', or 'expert'
payment_verifiedNoFilter to show only jobs from clients with verified payment methods
posted_within_hoursNoFilter jobs posted within the last N hours (max 720 = 30 days)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior. The description adds useful behavior beyond annotations by covering empty results ('No jobs found') and authentication failure handling. It does not mention rate limits or result ordering, but the annotations lower the burden and the added error 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.

Conciseness3/5

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

The description is well-structured with a front-loaded summary, Args section, Returns, Examples, and Error Handling. However, the Args section largely duplicates the input schema's parameter descriptions, making the overall description longer than necessary. The examples and error handling earn their place, but the redundancy costs conciseness.

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 13-parameter tool with no output schema, the description covers all parameters, return values, examples, and error cases. It does not fully clarify how empty results differ between markdown and json response formats, and it omits sorting behavior, but overall it is sufficiently complete for correct invocation.

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%, so the baseline is 3. The description adds value beyond the schema through realistic examples like query="react developer" with skills, high-budget fixed jobs, and recent expert jobs, which help an agent construct meaningful searches.

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 states a specific verb and resource: 'Search for freelance jobs on Upwork' and 'searches the Upwork job marketplace and returns matching job listings.' This distinguishes it from get/contract/profile tools, but it does not explicitly differentiate it from related job-listing tools like upwork_get_job_recommendations or upwork_list_saved_jobs.

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 says 'Use it to find opportunities based on skills, budget, category, and more,' which provides clear context for when to call it. It does not, however, state when not to use it or name alternative tools for specific scenarios.

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