Skip to main content
Glama

Jobiba Hiring: Post Jobs, Screen Applicants & Source Talent

Employer dashboard

employer_dashboard
Read-onlyIdempotent

Hiring snapshot: plan, wallet, active jobs vs limit, applications by stage, last-30-day impressions/clicks/apply clicks, top jobs and which premium features are on.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: it discloses the composition of the payload and the fixed 30-day window on impressions/clicks/apply clicks. It lacks any note on data freshness or whether it fails for non-employer accounts, which keeps it from a 5.

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?

One front-loaded sentence with a leading label followed by a compact enumeration; nothing is padded or repeated. The fragment style (no verb) is slightly less scannable than a full clause but wastes no words.

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 parameters and no output schema, the description carries the burden of describing the return payload, and it does so by listing each data section. What remains unstated (format, ordering, empty-state behavior) is minor for a low-risk read-only overview.

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 there is no parameter semantics to explain and the baseline of 4 applies. The description correctly implies the scope is the caller's own employer account rather than a parameterized entity.

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 enumerates the resource precisely: plan, wallet, active jobs vs limit, applications by stage, 30-day engagement metrics, top jobs, and enabled premium features. An agent can tell it is an aggregate employer overview rather than a single-resource getter. It stops short of a clear verb and never distinguishes itself from overlapping siblings like get_my_plan or list_my_jobs, which also return pieces of this data.

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?

The word 'snapshot' implies this is the at-a-glance overview rather than a detailed drill-down, which gives implicit usage guidance. However, there is no explicit when-to-use statement and no routing away from siblings that overlap (get_my_plan for plan state, list_my_jobs for job counts).

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.