Skip to main content
Glama
Sign In

JobMojito

by com.jobmojito
OverviewDiscussionsAdmin

List the company's users

list_users
Read-onlyIdempotent

[Admin] The company's users (owners, recruiters, hiring managers, admins) with the profile_id other tools take: a task assignee, a mention, an interviewer, a recruiter, a hiring team member. filter_text searches name and e-mail. role is the company-wide access level (reader = a hiring manager, read only); for who does what on one position pass position_id: only the people on it, each with position_roles (owning_recruiter, and the hiring team roles recruiter, hiring_manager, interviewer...).

Every argument in full, with examples: get_tool_reference.

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": "list_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoOnly users with this role.
llm_modelNoYour model id, e.g. "claude-opus-4-8"; "unknown" if unsure. For analytics.
filter_textNoOnly users whose name or e-mail contains this text.
merchant_idNoOptional merchant to scope to. Admins and sub-merchant operators only; other callers always use their token's merchant.
position_idNoOnly the users with a role on this multi-stage position (from list_interviews), each with position_roles.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.
include_inactiveNotrue: also invited and disabled users (deleted ones never).

Output Schema

NameRequiredDescriptionDefault
dataYes
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

The [Admin] prefix discloses a permission requirement that the annotations (readOnly/openWorld/idempotent) do not cover, and the reader role is clarified as a read-only hiring manager, which is useful context. Beyond that the description does not expand on pagination, result size, or ordering, which matters for a listing tool aimed at company-wide data. With annotations already covering the safety profile, a 3 is appropriate.

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 description is front-loaded with the tool's purpose and the payoff (profile_id), and the filter semantics follow in a dense but readable second sentence. The closing pointer to get_tool_reference is borderline filler for an agent that already has the schema, but it is a single short sentence.

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?

An output schema exists, so return values need not be explained, and the description still usefully names profile_id and position_roles as payload elements. For a seven-parameter admin listing tool with 100% schema coverage, the main remaining gap is guidance on result size or pagination, which the description never mentions.

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?

Coverage is 100%, so the baseline is 3, but the description adds real meaning on top of the schema: the role-to-title mapping (reader is a hiring manager), and that position_id also expands position_roles such as owning_recruiter, recruiter, hiring_manager, and interviewer. It does not explain include_inactive or merchant_id scoping beyond what the schema already states.

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

Purpose5/5

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

The description gives a concrete resource (the company's users) plus the enumeration of roles and the reason it matters: it returns the profile_id that other tools consume as assignee, mention, interviewer, recruiter, or hiring team member. That framing lets an agent tell it apart from list_candidates or list_interviews without opening any schema.

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 tells when to use each filter: filter_text for name or e-mail search, role for company-wide access level, and position_id for who does what on one position. It does not explicitly say when not to use the tool or name a sibling alternative for user lookup, so it falls short of a 5.

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

All JobMojito toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources