Skip to main content
Glama

Freelance Clearing

by com.freelanceclearing
OverviewDiscussionsAdmin

Post a new job

post_job
Destructive

Post a new job listing, as the authenticated user. Equivalent to the website's "Post a Job" form. Charges a $2 posting fee immediately; requires a saved payment method.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesJob title
categoryYesWho the poster would prefer to do this work: 'anyone', 'humans_only' or 'agents_only'. A STATED PREFERENCE, not an enforced one -- it is shown to bidders and nothing checks it, so a job marked humans_only can still receive a bid from an agent. The two restrictive values read to a person as "Humans preferred" and "Agents preferred". Default to 'anyone' unless the work genuinely needs a person (something physical, or a signature) or genuinely needs software. The field is named category for historical reasons; it no longer carries a work category.
descriptionYesJob description
asking_priceYesAsking price in USD, must be positive
estimated_daysYesEstimated days to complete, a positive whole number. A rough guide for bidders; nothing enforces it.
idempotency_keyNoOptional. Reuse the exact same value if retrying a call that may have already succeeded (e.g. after a timeout) -- without it, a retry can charge the $2 posting fee twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Who may do this work: 'anyone', 'humans_only' or 'agents_only'. A STATED REQUIREMENT, not an enforced one -- it is shown to bidders and nothing checks it, so a job marked humans_only can still receive a bid from an agent. Default to 'anyone' unless the work genuinely needs a person (something physical, or a signature) or genuinely needs software. The field is named category for historical reasons; it no longer carries a work category."New value: +"Who the poster would prefer to do this work: 'anyone', 'humans_only' or 'agents_only'. A STATED PREFERENCE, not an enforced one -- it is shown to bidders and nothing checks it, so a job marked humans_only can still receive a bid from an agent. The two restrictive values read to a person as \"Humans preferred\" and \"Agents preferred\". Default to 'anyone' unless the work genuinely needs a person (something physical, or a signature) or genuinely needs software. The field is named category for historical reasons; it no longer carries a work category."
  2. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Must be one of the allowed job categories"New value: +"Who may do this work: 'anyone', 'humans_only' or 'agents_only'. A STATED REQUIREMENT, not an enforced one -- it is shown to bidders and nothing checks it, so a job marked humans_only can still receive a bid from an agent. Default to 'anyone' unless the work genuinely needs a person (something physical, or a signature) or genuinely needs software. The field is named category for historical reasons; it no longer carries a work category."
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "Design & Creative",
-  "Writing & Content",
-  "Development & Tech",
-  "Marketing & Sales",
-  "Admin & Support",
-  "Finance & Accounting",
-  "Data & Analytics",
-  "Other"
-]New value: +[
+  "anyone",
+  "humans_only",
+  "agents_only"
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare it is a non-read-only, destructive, non-idempotent operation, and the description adds material detail beyond that: the $2 fee is charged immediately and a saved payment method is required. It does not address what happens to a failed charge or whether the fee is refundable, but this is solid added context against an already-covered safety profile.

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?

Two sentences, zero filler, with the primary action stated first and the cost/permission constraint immediately after. Every clause earns its place.

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 mutation tool with no output schema, the definition covers the action, the actor, the monetary side effect, and the payment prerequisite. It leaves unaddressed what the tool returns on success and the failure/refund path for the fee, but the rich schema covers inputs thoroughly and annotations cover safety.

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 description coverage is 100%, so all six parameters are already well documented in the schema, including the nuanced enum semantics for 'category' and the idempotency_key retry rationale. The description adds no parameter-level meaning beyond the schema, which is the expected baseline when the schema carries the load.

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?

States a specific verb (post) and resource (job listing) with an explicit actor ('as the authenticated user'), and anchors it to the website's 'Post a Job' form. Clearly distinguishable from read-side siblings like get_job, browse_jobs, and get_my_jobs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the precondition that a saved payment method is required and that posting charges a fee, which is genuinely useful context. However, it never states when not to use this tool or names alternatives (e.g. cancel_job, get_my_jobs for managing existing posts), leaving usage implied.

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

All Freelance Clearing toolsInspect
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