Skip to main content
Glama
Sign In

Tradify MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Update job status

update_job_status
Destructive

Set a status on a job, built-in or one of your custom statuses. Sets a job's status, as Change Status on the Jobs list does: to_invoice, on_hold, complete, cancelled, the others of the built-in list, or the name of a custom status from Settings > Jobs > Job Statuses (spaces as underscores). It reaches no one, and one more call sets it back.

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": {
      "job_id": "<job_id>",
      "status": "<status>"
    },
    "name": "update_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesJob ID from list_jobs.
statusYesunassigned, assigned, scheduled, in_progress, to_invoice, on_hold, complete, cancelled or the name of a custom status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true. The description adds meaningful context beyond those: 'It reaches no one' (no notifications are sent) and 'one more call sets it back' (the change is reversible). This helps an agent understand side effects and recovery.

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 front-loaded and appropriately sized for a simple mutation tool. The first two sentences are slightly redundant ('Set a status on a job… Sets a job's status…'), but the rest earns its place with examples and caveats.

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 two-parameter mutation with full schema coverage and rich annotations, the description covers status naming, custom status conventions, reversibility, and notification behavior. It does not mention permission requirements or invalid-status behavior, but those are minor gaps given the available structured data.

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. The description adds useful detail beyond the schema by explaining that custom statuses come from Settings > Jobs > Job Statuses and that spaces are rendered as underscores, which is not captured in the schema's status description.

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 states a specific verb and resource ('Set a status on a job') and immediately scopes it to built-in or custom statuses, mirroring the 'Change Status' action on the Jobs list. It is clearly distinct from sibling tools like get_job or create_job without needing to open the schema.

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?

Usage is implied by the reference to 'Change Status on the Jobs list,' and the reversibility note hints at when it is safe to call. However, there is no explicit guidance on when to use this versus alternatives (e.g., schedule_appointment) or any exclusions.

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

All Tradify MCP Server and API by Cotlet 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