Skip to main content
Glama
fieldjoshua

Upwork MCP Server

by fieldjoshua
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Milestones

upwork_list_milestones
Read-onlyIdempotent

List milestones for a fixed-price contract, with optional status filtering. View descriptions, amounts, and statuses to track contract progress.

Instructions

List milestones for a fixed-price contract.

View all milestones, their status, and amounts.

Args:

  • contract_id (string, required): The contract ID

  • status (string, optional): Filter by status: 'active', 'submitted', 'approved', 'paid', 'cancelled'

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

Returns: List of milestones with descriptions, amounts, and status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by milestone status
contract_idYesThe unique identifier of the contract
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.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior; the description adds that this reads milestone statuses and amounts for a fixed-price contract and can return markdown or JSON. No behavioral surprises 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.

Conciseness4/5

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

The description is compact and front-loaded with the core purpose. The Args and Returns sections are somewhat redundant with the schema but are short and useful for quick scanning.

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 read-only listing tool with strong annotations and full schema coverage, the description covers purpose, filter values, output format, and return content. It doesn't need extensive detail since there is no output schema and no destructive behavior.

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%, so the schema fully documents contract_id, status, and response_format. The description repeats those details rather than adding new semantic meaning, which meets the baseline but doesn't elevate it.

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?

Description uses explicit verb 'List' with specific resource 'milestones' scoped to 'a fixed-price contract', and clarifies the returned data (statuses and amounts). This distinguishes it from sibling tools like upwork_submit_milestone or upwork_get_contract.

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 establishes when to use it: viewing milestones on a fixed-price contract. It doesn't explicitly exclude alternatives, but the scoping and read-only nature make the intended use clear.

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