Skip to main content
Glama

List jobs in CrewNest

crewnest_list_jobs
Read-onlyIdempotent

List jobs 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_list_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotent and non-destructive, so the safety profile is known. The description genuinely adds that nothing is opened or executed server-side and that the return is procedural guidance rather than data — useful context. The closing paragraph about an unrelated "official Job Pricing MCP server" describes third-party tools, not this tool, and mostly adds noise/misdirection.

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

Conciseness2/5

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

The core behavior is in the first two sentences and front-loaded, but the third sentence is promotional filler about a separate CrewNest official API and does not help an agent select or invoke this tool. The two opening sentences also pack several unrelated clauses (audience list, return shape, execution contract) into one long run-on.

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?

It covers the essentials for a zero-parameter read-only tool: what comes back (step-by-step screens/buttons/fields) and that the agent must follow up with browser tools. It does not say what form that guidance takes, how large it is, or who the "user's own CrewNest account" must be authenticated as, and there is no output schema to lean on.

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 input schema has zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the definition correctly makes no claims about inputs.

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

Purpose3/5

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

The name and title say "list jobs," but the description says the tool "Returns how to do it in CrewNest step by step (screens, buttons, fields) and opens nothing by itself" — i.e., it returns instructions, not job records. That behavior is stated concretely, yet the mismatch with the name leaves real ambiguity about what an agent will actually receive. It also gives no differentiation from the many crewnest_list_* siblings.

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?

There is a usable workflow hint: this tool only returns guidance, and the agent must then act via cotlet_browser_* tools in the CrewNest Cloud Browser. However, nothing says when to prefer this over sibling listers (crewnest_list_crew, crewnest_list_activity, etc.) and no conditions or exclusions are stated.

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