JobMojito

Get merchant status

get_merchant_status

Read-onlyIdempotent

[Admin] Get a merchant status snapshot: credit balances, subscription, pending-work counts, candidate/result totals, and invitation headroom.

Status snapshot for a merchant: interview-credit balances, subscription type/status, pending-work counts (undecided / ongoing / uncredited interviews), candidate & result totals with 14-day history, and invitation headroom. Scoped to your token's merchant (or a merchant_id override for admins / sub-merchant operators). Also echoes the caller's profile_id and default_merchant_id from the token, plus the effective merchant_id.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`merchant_id`	No	Optional merchant to scope to. Admins and sub-merchant operators only; other callers always use their token's merchant.

Output Schema

TableJSON Schema

Name	Required	Description
`candidates`	Yes	Total candidates (non-archived profile_interview rows) for the merchant.
`profile_id`	Yes	The calling user's profile id (auth user id), taken from the JWT.
`merchant_id`	Yes	The merchant this status is scoped to — the default_merchant_id unless an admin / sub-merchant operator overrode it via the merchant_id query param.
`invitations_sent`	Yes	Interview invitations sent during the current subscription period.
`interview_results`	Yes	Total non-archived interview results for the merchant.
`invitations_limit`	Yes	Maximum invitations allowed this period (4x available credits). Null for unlimited (Special) plans.
`subscription_type`	Yes	Subscription plan name (e.g. Free, Starter, Growth, Special).
`candidates_history`	Yes	Daily new-candidate counts for the last 14 days, most recent first.
`definitions_active`	Yes	Count of active interview + position definitions.
`interviews_ongoing`	Yes	Interviews currently in progress (coach_status = started).
`default_merchant_id`	Yes	The caller's home merchant id pinned in the JWT (app_metadata.merchant_id). Null if the token carries no merchant.
`subscription_status`	Yes	Subscription status (e.g. active, past_due, canceled). Null when no subscription.
`interviews_undecided`	Yes	Completed interviews awaiting a recruiter decision.
`invitations_available`	Yes	Remaining invitations this period. Null for unlimited (Special) plans.
`credits_interview_extra`	Yes	Extra (top-up) interview credits available on top of the monthly allowance.
`credits_interview_single`	Yes	Single-position interview credits available.
`interview_result_history`	Yes	Daily new-interview-result counts for the last 14 days, most recent first.
`credits_interview_monthly`	Yes	Remaining monthly interview credits.
`interviews_without_credits`	Yes	Completed interviews that have not yet consumed a credit.
`credits_interview_monthly_limit`	Yes	Monthly interview-credit allowance for the current plan.

TDQS

A4.7/5.0

Behavior5/5

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

Annotations include readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. Description adds that the tool echoes caller's profile_id and default_merchant_id, and clarifies authorization boundaries for the merchant_id parameter. No contradictions with annotations.

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

Conciseness5/5

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

The description is two sentences: a high-level summary followed by a detailed list of components. It is front-loaded with the purpose and succinctly expands without unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description need not cover return values. It fully describes all components of the snapshot and the caller info echo, making it complete for a read-only, idempotent tool.

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?

Schema coverage is 100% with description for the only parameter (merchant_id). The tool description adds valuable context about who can use the override (admins/sub-merchant operators), improving clarity beyond the schema.

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 clearly states it retrieves a 'merchant status snapshot' and lists specific components like credit balances, subscription, pending-work counts, etc. It distinguishes from sibling tools such as 'get_merchant_analytics' and 'get_merchant_credit_usage' by detailing the unique fields included.

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?

The description explains scope: default to token's merchant, with optional merchant_id for admins/sub-merchant operators. While it doesn't explicitly name alternatives, it provides clear context on when to use the optional parameter and who can use it.

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

All JobMojito tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation4/5

Most tools target distinct resources and actions, with clear category prefixes like [Interviews], [Results], and [Admin]. A few pairs could be confused—create_interview vs. create_interview_from_questions and update_interview vs. set_interview_state—but the descriptions do enough to separate them.

Naming Consistency4/5

The overwhelming majority follow a consistent verb_noun pattern: create_*, get_*, list_*, update_*, generate_*. The main deviation is jobmojito_configuration, which is a noun phrase rather than an action verb, and a few longer names like request_another_interview_attempt break the clean pattern slightly.

Tool Count2/5

With 29 tools, this server is above the 25+ threshold and places a significant navigation burden on an agent. The tools are organized into coherent domains, but several admin/merchant and results tools could likely be consolidated.

Completeness3/5

The core interview lifecycle is well covered: create, read, update, list, state changes, result retrieval, and report generation. However, there are notable gaps such as no delete operations for interviews or catalogue directories, no candidate management beyond listing/registration, and no explicit result-decision tool.

Get merchant status

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources