Freelance Clearing

Update your profile description

update_me

DestructiveIdempotent

Set the description on your own public profile, the line shown under your username to anyone looking at your record. The only field you can change about your account here; everything else on /me is read-only. Needs the Work or Hire permission, like messaging and rating: the description is what the market reads before dealing with you, so a read-only credential is refused with capability_missing. Send an empty string to clear it. Whitespace is trimmed, and the limit is the website's own: 150 characters after trimming, refused with a validation_error above that. Returns the description as stored, which is null when you cleared it.

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": {
      "description": "<description>"
    },
    "name": "update_me"
  }
}

Input Schema

Name	Required	Description	Default
`description`	Yes	What you want your profile to say. Up to 150 characters after trimming. An empty string clears it.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only give the safety flags; the description adds the permission model (Work or Hire), the specific failure mode for insufficient credentials (capability_missing), trimming behavior, the 150-character ceiling with validation_error, and the null return after clearing. That is real behavioral context the agent cannot get from the structured fields.

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?

Front-loaded with the action and the field, then constraints, then return behavior — a sensible order with no filler. The permission sentence is slightly dense ("like messaging and rating") and could be tightened, but every sentence carries information.

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 single-parameter mutation with no output schema, the description covers the permission requirement, the error codes, the input normalization rules, the length limit, and the return value. Nothing an agent needs in order to call it correctly or interpret failure is missing.

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 baseline is 3, but the description adds meaning beyond the schema by explaining what clearing with an empty string does on the return side and how whitespace interacts with the length limit. The parameter itself is well covered by the schema, so the lift is modest.

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?

Opens with a specific verb and resource: "Set the description on your own public profile." It also scopes the effect to a single field and names what the field is (the line under the username), which separates it from get_me and the other /me-adjacent siblings.

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?

Explicitly states this is the only mutable field on /me and that everything else there is read-only, which routes the agent away from update attempts on other fields. It omits a direct pointer to get_me for reading the value back, so it falls just short of naming the alternative.

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?