Skip to main content
Glama

Update job status in CrewNest

crewnest_update_job_status
Read-onlyIdempotent

Update job status in the user's own CrewNest account from ChatGPT, Claude or any AI agent. Returns how to do it in CrewNest step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser. CrewNest's official API: CrewNest publishes an official, free Job Pricing MCP server with three read-only tools for public price calculations and benchmarks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "crewnest_update_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true; the description explains why — it 'opens nothing by itself' and only returns guidance — which resolves the apparent tension with the 'update' name. It also names the required follow-up actor (the Cloud Browser in the user's own account), adding context the annotations cannot express. It omits what happens if the browser is not connected or not authenticated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The operational core is front-loaded and useful, but the closing sentence about CrewNest's official free Job Pricing MCP server and its three read-only tools has no bearing on invoking this tool and reads as promotion. Removing it would make the definition sharper without losing any calling information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter orchestration tool with no output schema, the description covers the handoff but leaves key pieces implicit: how the relevant job is selected, what the returned steps look like, and any prerequisites such as an active Cloud Browser session or login. Adequate to attempt a call, not complete enough to guarantee a correct one.

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?

The schema takes no parameters, so there is nothing to document and the baseline is 4. The description does not address the natural question of how the target job is identified with zero inputs, but this is a scope question rather than missing parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description makes clear that despite the 'update job status' name, the tool's actual action is to return step-by-step CrewNest instructions (screens, buttons, fields) and that the real mutation happens via cotlet_browser_* tools. That is a specific verb-plus-resource statement an agent can act on. It stops short of 5 because it never says which job it applies to, so the 'job status' scope stays abstract.

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?

It gives one clear sequencing rule: call this first, then perform the change with the cotlet_browser_* tools in the user's CrewNest Cloud Browser — a real usage signal. It offers no exclusions, however, and does not say when to prefer status-changing siblings such as crewnest_cancel_job or crewnest_reschedule_job over this path.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources