Skip to main content
Glama

Bulk assign jobs in CrewNest

crewnest_bulk_assign_jobs
Read-onlyIdempotent

Bulk assign 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_bulk_assign_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with the non-obvious disclosure that it 'opens nothing by itself' and only returns procedural guidance. It also names the downstream tool family needed to actually complete the task. It stops short of describing the return payload's shape or any limits on job count, but the key behavioral surprise (no side effects despite the 'assign' name) is well covered.

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 load-bearing content is the first two clauses: it returns instructions and does nothing itself, then hands off to cotlet_browser_* tools. The closing sentence about CrewNest's separate free Job Pricing MCP server is promotional and irrelevant to selecting or invoking this tool, and the semicolon-chained phrasing makes the key handoff harder to scan.

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 input schema, no output schema, and a simple guidance-returning behavior, the description covers what an agent needs: what it returns, that it has no side effects, and what to use next. It lacks only the single-vs-bulk routing rule against crewnest_assign_job.

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 tool takes zero parameters, so by the stated baseline this dimension sits at 4. There is nothing for the description to disambiguate, and it correctly avoids inventing parameter detail that doesn't exist.

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 the concrete operation (bulk assigning jobs) and, crucially, clarifies that the tool returns step-by-step CrewNest instructions rather than performing the assignment. It does not explicitly distinguish itself from the sibling crewnest_assign_job (single assignment), so an agent must infer that boundary, but the core purpose is unambiguous.

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?

It gives a clear usage chain: call this to get the CrewNest screens/buttons/fields, then act via cotlet_browser_* tools in the Cloud Browser. What's missing is a when-not / alternative statement, such as when a single assignment (crewnest_assign_job) is the better fit instead of bulk.

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