Skip to main content
Glama
fieldjoshua

Upwork MCP Server

by fieldjoshua
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Proposals

upwork_list_proposals
Read-onlyIdempotent

Retrieve your submitted Upwork proposals and view job applications with current status. Filter by pending, accepted, declined, withdrawn, or archived to track bid outcomes.

Instructions

List your submitted proposals on Upwork.

View all your job applications and their current status.

Args:

  • status (string, optional): Filter by status: 'pending', 'accepted', 'declined', 'withdrawn', 'archived'

  • 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 proposals with job titles, bid amounts, and status.

Examples:

  • All pending proposals: status="pending"

  • Recent accepted proposals: status="accepted", limit=10

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of proposals to return (default: 20)
offsetNoNumber of results to skip for pagination
statusNoFilter by proposal status: 'pending', 'accepted', 'declined', 'withdrawn', or 'archived'
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description reinforces this with 'List' and 'View', and additionally discloses the return content ('job titles, bid amounts, and status'). No hidden side effects or contradictions are present.

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 well-structured with an opening summary, Args section, Returns section, and Examples. Every section is purposeful and no content is redundant or wasted. The most important information is front-loaded.

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?

For a read-only list operation with all parameters covered by the schema and annotations disclosing the safety profile, the description is complete. It specifies the response fields, parameter behavior, and examples, so an agent has everything needed to call it correctly.

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 schema already documents all parameters. The description adds value by providing concrete examples (status='pending', status='accepted', limit=10) and summarizing defaults and limits in an agent-friendly way.

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 action ('List your submitted proposals'), the resource ('proposals on Upwork'), and the purpose ('View all your job applications and their current status'). It is immediately distinguishable from sibling tools like upwork_get_proposal by its plural, list-oriented scope.

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 makes clear when to use this tool: when the agent needs to view all submitted proposals or filter them by status. It does not explicitly mention alternatives such as upwork_get_proposal for a single proposal, but the context is strong enough that usage is not ambiguous.

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