Skip to main content
Glama

Generate customer portal link in CrewNest

crewnest_generate_customer_portal_link
Read-onlyIdempotent

Generate customer portal link 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_generate_customer_portal_link"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With readOnlyHint/idempotent/destructive=false already declared, the description still adds real value by disclosing what the call returns (screens, buttons, fields) and that it performs no side effect — important since there is no output schema. The closing sentence about CrewNest's 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.

Conciseness4/5

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

The operative guidance is front-loaded in the first two sentences and is dense but useful. The trailing sentence advertising the official Job Pricing MCP server is off-topic for this tool and dilutes the 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?

For a zero-parameter, non-mutating tool with no output schema, the description covers what it returns, that it mutates nothing, and what to do next. Only minor gaps remain, such as whether any prerequisite (e.g., an existing customer record) is required before the generated steps apply.

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 and the schema is empty, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly implies no inputs are needed.

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 (generate a customer portal link) and clarifies the crucial nuance that the tool returns step-by-step instructions rather than performing the action. It does not, however, distinguish itself from near-neighbors like crewnest_read_customer_portal or crewnest_get_payment_link that an agent might reasonably confuse it with.

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 explicit workflow routing: use this tool to get the steps, then execute them with the cotlet_browser_* tools in the Cloud Browser, and it states plainly that this tool 'opens nothing by itself.' It stops short of saying when NOT to use it or which Crewnest sibling covers related link needs.

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