Skip to main content
Glama

Update job notes in CrewNest

crewnest_update_job_notes
Read-onlyIdempotent

Update job notes 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_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnlyHint/idempotentHint annotations, the description discloses the crucial behavior that this tool 'opens nothing by itself' and only returns navigation steps (screens, buttons, fields), requiring browser tools to actually apply the change. That resolves the tension between the mutating-sounding name and the read-only annotation. The closing sentence about a separate Job Pricing MCP server adds no behavioral information about this tool.

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 first two sentences are dense but earn their place, front-loading what the tool returns and how to follow up. The third sentence about CrewNest's official Job Pricing API is off-topic promotion that does not help an agent select or invoke this tool, diluting an otherwise tight definition.

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?

With no parameters, no output schema and annotations covering the safety profile, the description supplies the essential missing piece: what is returned (step-by-step UI instructions) and the follow-up path. Minor gaps remain around prerequisites and error behavior, but nothing critical to correct invocation is absent.

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 has zero parameters, so there is nothing for the description to disambiguate; the baseline applies. It correctly implies no inputs are needed to retrieve the walkthrough.

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 names a specific verb and resource ('Update job notes in the user's own CrewNest account') and clarifies the mechanism: it returns step-by-step instructions rather than performing the change. It does not explicitly contrast with siblings such as crewnest_update_job_status, so it stops short of full differentiation.

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 tells the agent to call this first and then act via the cotlet_browser_* tools in the CrewNest Cloud Browser, which is real sequencing guidance. It gives no when-not conditions or prerequisites (e.g., whether the user must be signed in), so usage is only implied.

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