Freelance Clearing

Get a user's offers

get_user_offers

Read-onlyIdempotent

List the offers one user has posted, active and ended -- the same list their profile's Offers tab shows to anyone. Rows are GET /offers' rows, so a caller that reads the market listing reads this one with no new parsing: each carries the seller's rating and completed count, and the offer's OWN record, completed_through and transacted_through, which are the jobs finished and the money moved through that listing rather than the seller's lifetime totals. DEFAULTS TO ANY STATUS, unlike browse_offers, which defaults to active: this is one account's record and the ended listings are the evidence it has been selling for a while. Active first, then ended, newest first within each. An offer cannot be edited, so a seller who changed their terms shows as an ended offer beside a newer one -- that is the ordinary case rather than a mistake. The REQUESTS on these offers are not here and are not public anywhere: a request is private between its buyer and its seller.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "username": "<username>"
    },
    "name": "get_user_offers"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Default 25, maximum 100.
`offset`	No	Default 0.
`status`	No	Default any, which is both. 'active' is the one that can take requests today; 'ended' is the closed record.
`username`	Yes	The user's public username rather than their UUID. Capitalization is ignored.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

changedInput schema / properties / username / description

Previous value: -"The user's public username, not their UUID. Matched exactly, including capitalization."New value: +"The user's public username rather than their UUID. Capitalization is ignored."

AddedOct 17, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, and the description adds real context beyond them: result ordering (active first, then ended, newest first within each), the row shape matching GET /offers, the crucial distinction that completed_through and transacted_through are per-listing rather than seller lifetime totals, and the fact that offers are immutable so duplicate-looking terms are normal.

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?

It is a single dense paragraph, but it is front-loaded with the scope, then the return shape, then the sibling contrast, and each sentence carries distinct information; the aside about edited terms appearing as an ended offer is slightly indulgent but still answers a real caller confusion.

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?

There is no output schema, so the description carries the full burden of describing return values, and it does: row provenance, per-offer rating and completion fields, ordering, pagination-adjacent scope, and an explicit boundary that private requests are not included anywhere.

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 limit/offset/username are already documented and a baseline of 3 applies; the description earns an extra point by spelling out the semantics of the status enum default ('any' = both, 'active' = can take requests today, 'ended' = closed record) and why 'any' is the right default here.

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 names a specific verb and resource ('List the offers one user has posted, active and ended') and immediately frames the scope as the profile's Offers tab, which lets an agent distinguish it from browse_offers without opening a schema.

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?

It states the selection rule explicitly ('one account's record and the ended listings are the evidence it has been selling for a while') and contrasts the default with the sibling ('DEFAULTS TO ANY STATUS, unlike browse_offers, which defaults to active'), so an agent knows both when to pick this tool and when not to.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Freelance Clearing tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?