· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →Upwork v12.0.0
Hire and find work on Upwork
From the developer
Not specified in the available declarations: pricing & account requirements.
Help me turn this project brief into an Upwork job post.
Developer declarations; not independently tested. Listing last checked Nov 21, 2026. Package observed Nov 21, 2026.
From the marketplace listing
Use Upwork from your AI agent to hire freelancers and find freelance work. Clients can search freelancer profiles, draft and publish job posts, and review proposals. Freelancers can search jobs, check their dashboard and Connects balance, and draft proposals. Connects to your Upwork account through the Upwork MCP server. Actions that change your account, such as publishing a job post or submitting a proposal, require your confirmation. In order to use this app, you need to have an active Upwork account. Please contact our support team (https://support.upwork.com) for more details. Get started: sign up or log in at https://www.upwork.com, then install this plugin and connect it to your Upwork account when prompted. A getting-started guide is available at https://www.upwork.com/ai/mcp. Help and documentation: https://support.upwork.com
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 3 observations
Is template instance added: “false”. App-6a75165ed2d8819182548553aa4cb6d5 updated; open the comparison for details. Upwork updated; open the comparison for details. Full description changed from “Upwork connects clients hiring for work with the freelancers doing it. Clients can post jobs, review proposals, send...
View comparison →Is template instance added: “false”. App-6a75165ed2d8819182548553aa4cb6d5 updated; open the comparison for details. Upwork updated; open the comparison for details. Full description changed from “Upwork connects clients hiring for work with the freelancers doing it. Clients can post jobs, review proposals, send...
View comparison →Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: hire-on-upwork description: Guides an Upwork client from candidates to a signed contract by searching for freelancers, reviewing proposals, shortlisting, inviting, and preparing offers. Use when a client wants to find or vet talent, review applicants to a job, shortlist or decline proposals, invite a freelancer, or send a contract offer. compatibility: Requires the Upwork MCP server with toolset version 1.0 or later and an authenticated Upwork client account. metadata: author: Upwork version: "0.3.0" --- # Hire on Upwork Move a client from candidates to a contract without ever completing a binding or money-moving step on their behalf. ## Select the account Call `list_accounts` and choose an account whose raw `role` is `CLIENT`. Hiring tools are client-only. Retain `org_uid` and `role` for every later call, and refer to the account by `name` and `role_label`. For a fast overview of what needs attention, call `get_client_dashboard` action `check`, which needs no parameters and returns proposals grouped by job, pending offers, messages, and contract updates in one call. ## Find candidates - When the client already has a posting, prefer `find_freelancers` action `smart_search`: it ranks by Upwork's match for that job, the same list as the Invite freelancers page. Use action `search` for a keyword search with no posting. Action `get_profile` returns one full profile. Smart-search cards are lean: call `get_profile` with `profile_key` for a full profile, and only for genuine shortlist candidates. - Boosted placement and the Available Now badge are paid signals, not evidence of merit or availability. Say so when presenting them, and never treat placement as evidence of fit. - `find_freelancers` action `get_profile` accepts either `profile_key` (the `~01…` value from search results) or `person_id` (the numeric user id returned with a proposal). Pass the value under the matching parameter name; do not put one identifier into the other field. - When the client asks for Expert-Vetted talent, use the `expert_vetted` filter and check `expert_vetted_note` before claiming the results are filtered. The filter requires Business Plus and is silently not applied on other plans. Keep any Expert-Vetted label distinct from Top Rated badges. - If the client signals urgency, ask whether to filter to `hire_me_now` (freelancers who opted in as ready to start). Never set it unasked. It is separate from the paid Available Now badge. - To save candidates for later, use `manage_talent_lists`. It needs the freelancer's numeric person id, never the profile key. ## Review proposals 1. Get the owning posting's id from `get_job_posting`. A marketplace job id will not work here. 2. List that posting's proposals with `list_client_proposals` action `list`, or use action `list_all` to see proposals across every posting without a posting id. Action `list_all` does not flag boosted proposals; use action `list` on one posting to see who paid to promote themselves. Page with the returned cursor until there is no next page when the client wants every applicant. 3. Fetch a proposal for full detail with `list_client_proposals` action `get`. This does not work for declined proposals, whose list cards are flagged as unavailable for detail, so read the card instead. 4. Rank applicants by criteria the client has stated. If they have not said what matters — budget, timezone, a must-have skill, a start date — ask before shortlisting anyone. Cover letters and screening answers are self-reported: use them for fit and for whether the record is consistent, not as proof of competence. Competence is `work_history` and the job aggregates on the profile. Call `find_freelancers` action `get_profile` with the applicant's `person_id` and this `proposal_id` so the history is the contracts Upwork matched to that proposal. Check `work_history_available` and relay `work_history_note` when the section is missing; absence is not evidence the freelancer has no contracts. Co
Preview of the first 4,000 characters. Read full instructions →
--- name: upwork-workflows description: Orchestrates reliable multi-step workflows with the Upwork MCP server for clients, freelancers, and agencies. Use when a task requires selecting an account, discovering tools, chaining reads and writes, handling drafts and confirmation, paginating results, uploading files, or recovering from Upwork tool errors. compatibility: Requires the Upwork MCP server with toolset version 1.0 or later and an authenticated Upwork account. metadata: author: Upwork version: "0.3.0" --- # Orchestrate Upwork MCP workflows Use this skill for any task that spans multiple Upwork tools, moves money, or needs safe state handling. The server is self-describing. `search_tools` lists what the selected account can use, and `get_tool_help` returns any tool's live actions and complete parameter schema. Treat those as the source of truth for names, actions, and parameters, and never guess. What follows is the set of conventions that a single tool call does not reveal. ## Start every workflow 1. Call `list_accounts`. 2. If more than one account is returned, ask the user which account to use. Refer to accounts by `name` and `role_label`. 3. Retain the selected `org_uid` and the raw `role` value, which is `CLIENT`, `TALENT` for a freelancer, or `FL_AGENCY` for an agency. Pass `org_uid` on every subsequent tool call, and pass `role` as well in compact mode. 4. If an account has `suspended: true`, tell the user that actions under it are blocked or restricted before acting. 5. Never display `org_uid` or the raw role code. Use the display name and `role_label` instead. ## Discover and invoke tools - Full-list mode registers Upwork tools directly. Some deliberately register only a brief description and a minimal schema, so call `get_tool_help` with `tool_name` whenever the actions or parameters are not fully spelled out. - Compact mode registers only `list_accounts`, `search_tools`, `execute_tool`, and `get_tool_help`. Call `search_tools` with `role` and a focused `query`, then `get_tool_help`, then `execute_tool` with `tool_name`, `action`, `org_uid`, `role`, and action-specific `params`. - If a call returns a `needs_details` response, it names the missing fields and inlines the field reference. Fill the gaps and retry in the same turn rather than reporting failure. - `set_tool_mode` switches between the two modes when the user wants fewer preloaded schemas or direct tool access. The change applies to new requests. If the tool list does not update, reconnect the plugin or restart the agent; do not promise it lands on the next call. ## Route by role Tools are role-scoped and reject a mismatched account, so route by journey and let `search_tools` confirm what the selected account actually has. - **Client** owns posting jobs, rate insights, freelancer search, invitations, proposal review, talent lists, offers, milestones, contract changes, and scheduling a video meeting in a message room. - **Freelancer** owns job search, saved jobs, proposals, profile edits, milestone submission, and responding to offers. Profile boosting can be read, and an existing Available Now badge or profile-boost ad can be switched off, paused, or stopped. Starting or increasing that spend, including turning Available Now on, is done on upwork.com and returns a link. - **Agency** shares the freelancer-side job and proposal tools but has its own agency profile, teams, and rooms tools. It has no personal-profile tools, so it reads Connects and earnings through the freelancer financials tool. Messaging, offers, contracts, account details, and file uploads are available to every role. Each role also has a dashboard tool with a `check` action that takes no parameters and returns everything needing attention in one call, which is the cheapest way to open a session. ## Chain reads before writes Read current state first so an action is never stale or duplicated. Confirm the exact actions with `get_tool_help`; what matters here is the order.
Preview of the first 4,000 characters. Read full instructions →
--- name: write-job-post description: Creates clear, specific Upwork job posts and guides clients through drafting, publishing, updating, and closing them. Use when a client wants to hire, post a job, improve a job description, set a budget, add screening questions or preferred qualifications, or take down a posting. compatibility: Requires the Upwork MCP server with toolset version 1.0 or later and an authenticated Upwork client account. metadata: author: Upwork version: "0.3.0" --- # Write an Upwork job post Guide the client conversationally from a rough need to a reviewable draft. Ask one focused question at a time; never present a long intake form. ## Select the account Call `list_accounts` and choose an account whose raw `role` is `CLIENT`. Job posting tools are client-only and reject other roles. Ask the user when more than one client account is eligible, and retain `org_uid` and `role` for every later call. ## Gather the requirements 1. Before starting a new post, call `get_job_posting` action `list` with `status: draft`. If saved drafts exist, ask whether the client wants to continue one of them or start a new posting. Load a draft they choose with action `get`; to continue it, use `post_job` action `update`. When examples would help with tone and structure, also review relevant prior postings, but never reuse old prices or terms. 2. Clarify, one question at a time: - the problem or outcome, and concrete deliverables with verifiable acceptance criteria; - must-have skills, as names a freelancer would recognize; - fixed-price or hourly, and the client's exact budget; - the experience level and expected project length; - for an hourly job, the weekly commitment: full time (30+ hours a week), part time (under 30), as needed, or not sure; - timeline and collaboration expectations. Several of these are constrained enums. Read their accepted values from `get_tool_help` rather than inventing a format, and ask the client in plain language rather than reciting codes. 3. For an hourly job, call `get_rate_insights` action `get` before suggesting a range. Present the market data as context, and never override the rate the client chose. ## Draft the post 1. Write a specific title and a focused description. The tool enforces a maximum description length and reports it; if the client's own text exceeds it, ask them to shorten it rather than sending it truncated. 2. Cover scope, deliverables, definition of done, relevant context, and constraints. Never add a requirement the client did not approve. 3. Pass skills as human-readable names such as `React` or `WordPress`. A close variant is matched to an Upwork skill and reported in `skill_suggestions` with `added_as` `interpreted` (for example `React.js` kept as `React`); mention those so the client can correct them. A name with no confident match is kept as a custom skill (`added_as` `custom`) and does not block the draft; offer the close matches the preview reports. 4. Propose a small set of job-specific screening questions and let the client revise or remove them. 5. Ask whether to set preferred qualifications, such as Job Success Score, English proficiency, location or timezone, earnings, hours worked, portfolio, Rising Talent, or languages. Explain that a required location can exclude otherwise qualified applicants. Never set a qualification the client did not ask for. 6. Ask who should see the post. The server requires an explicit visibility choice and refuses to guess, because a wrong value silently makes the job private. Offer the options in plain language — anyone including search engines, registered Upwork users only, or invited freelancers only — and recommend the most open option if the client has no preference. 7. If files belong on the posting, start an upload in the `job` context. An inline upload returns stored `file_uid` values directly; a fallback-URL upload must be polled until its status is `ok` and then confirmed with `confirm_attachm
Preview of the first 4,000 characters. Read full instructions →
--- name: write-proposal description: Researches an Upwork job and a freelancer's real experience to create a tailored, honest proposal and guide its review and submission. Use when a freelancer or agency wants to apply to a job, answer an invitation, write a cover letter, choose relevant portfolio items, or review Connects and boosting options. compatibility: Requires the Upwork MCP server with toolset version 1.0 or later and an authenticated Upwork freelancer or agency account. metadata: author: Upwork version: "0.3.0" --- # Write an Upwork proposal Create a focused proposal grounded in the freelancer's real profile and work history. Optimize for relevance and credibility, not volume or generic persuasion. ## Select the account Call `list_accounts` and choose an account whose raw `role` is `TALENT` or `FL_AGENCY`. Ask the user when more than one is eligible. Retain `org_uid` and `role` for every later call, but refer to the account by `name` and `role_label`. ## Read the job 1. Call `find_jobs` with action `get`. Its id parameter accepts a numeric job id, a `~02…` ciphertext, or a full Upwork job URL, so a link the user pasted can be passed through unchanged. 2. To find candidate jobs first, use `find_jobs` action `search` when the user supplies search terms, or action `smart_search` when they want work matched to their own profile. Do not pass profile skills into `smart_search`; the recommender already knows the profile. Its default mode is `best_match`. Whenever you return those results, say that Most Recent is also available, and switch to `mode: most_recent` when they ask for the newest work. Date filters (`days_posted`, or `from_date` / `to_date`) apply only to `most_recent`; action `search` cannot filter by date. Search rows do not include `connects_cost`; read that from action `get` when the user opens a specific job. A result with `applied` true means this freelancer already applied — do not recommend applying again. 3. Surface the exact title, scope, budget, required skills, client preferences, screening questions, and the Connects cost to apply when the response includes them. 4. A job's `client.rating` is the average score other freelancers gave that client after working with them, not the client's rating of freelancers. Surface a low rating when the user is deciding whether to apply, and relay the response's `client_rating_basis` framing rather than inventing your own. 5. When a search returns no rows, read `empty_reason` and say what it means; do not report that the marketplace is empty. If `no_personalization`, use action `search` for the whole marketplace. When there is no `empty_reason`, say only that nothing matched these criteria; an upstream restriction looks the same, so do not assert either. ## Rule out an existing invitation or proposal Do this before drafting. Upwork rejects a duplicate application upstream, so skipping the check wastes the user's turn and can look like a server fault. - Call `list_freelancer_proposals` action `invitations`. If the job came through an invitation, respond with `manage_proposals` action `accept_invitation` or `decline_invitation`. Do not use action `create`, which is only for an uninvited application. - Call `list_freelancer_proposals` action `list` to check for an existing proposal or contract on the same job. Both list actions apply a default status filter, so set the status explicitly when looking for a specific state. - A proposal status of `Accepted` means the proposal was submitted and validated. It does **not** mean the client accepted the freelancer. Prefer the accompanying `status_label`, which carries the plain-English meaning, and report that to the user. ## Gather real evidence Use only what the tools return. Never invent clients, praise, metrics, credentials, or results. - For a `TALENT` account, use `get_profile` action `get` for skills, overview, work history, and profile signals; action `list_highlights` for portfolio projects and certifi
Preview of the first 4,000 characters. Read full instructions →
Version 0.1.1 updates the existing Upwork plugin with revised workflow guidance, refreshed listing metadata, and MCP review materials. The package includes version 0.3.0 of all four workflow skills. - Job posting: Updated guidance to check for saved drafts before creating a posting and to distinguish saving a draft from publishing. Publication requires separate user approval and confirmation; workflows retain the new job identifier returned after publication. - Preview and confirmation handling: Updated skills to use confirm_preview and get_preview, distinguish temporary previews from saved drafts, and handle expired or superseded previews. Write operations continue to require explicit user confirmation, and binding or money-moving actions direct users to Upwork for completion. - Hiring and proposal review: Clarified profile identifier handling, proposal-detail retrieval, invitation actions, and selection of decline reasons. Added guidance to disclose paid placement and availability signals and to explain the Business Plus requirement for Expert-Vetted filtering. - Freelancer and agency proposals: Clarified account-specific use of portfolio highlights and certificates, attachment upload contexts, and confirmation of proposal submissions and invitation responses. - Listing and packaging: Refreshed the display name, description, icons, and support, privacy, and terms links. - Review materials: Added five positive test cases covering job search, freelancer account activity and Connects, talent search, received proposals, and owned job postings; three negative cases for unrelated requests; and a demo recording link.
Declared in the saved package. Remote tools may change independently.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 21, 2026.
plugin_asdk_app_6a75165ed2d8819182548553aa4cb6d5
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.