Skip to main content
Glama
jobinja-mcp

jobinja-mcp

by sepehr071

Company profile

jj_company
Read-onlyIdempotent

Read a company's Jobinja profile to get its industry, size, website, open job count, and intro/culture text by supplying the company slug.

Instructions

Read a company's Jobinja profile: industry, size, website, open job count and intro/culture text.

No reviews exist; the only rating is jj_top_companies.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "jj_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesCompany slug, e.g. payampardaz.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / slug / description
      Previous value: -"Company slug from a Jobinja company or job URL, e.g. payampardaz."New value: +"Company slug, e.g. payampardaz."
  2. First observedv0.1.1

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, openWorldHint and destructiveHint=false, so safety is covered. The description adds value beyond that by scoping exactly what data exists and explicitly warning that no reviews exist, preventing a wasted call or a fabricated expectation.

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?

Two sentences, front-loaded with the core action and field list, with the caveat about ratings second. Nothing is wasted and nothing is repeated from the structured fields.

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 output schema, the description correctly enumerates the returned fields so the agent can judge relevance without calling. The only gap is behavior on an unknown or invalid slug, which is relevant given openWorldHint=true and a read tool keyed on a free-form slug.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single slug parameter already carries a pattern and an example, so the description adds no syntax or format detail. Baseline 3 applies since the schema does all the parameter work.

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 states a specific verb and resource ("Read a company's Jobinja profile") and enumerates the exact fields returned (industry, size, website, open job count, intro/culture text), so the agent knows precisely what it gets. It distinguishes itself from jj_top_companies for ratings but never names jj_company_jobs, which is the closest sibling and could be confused with the "open job count" field.

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?

Usage is only implied: given a company slug, fetch its profile. One alternative is named (jj_top_companies for ratings), which is genuinely helpful routing, but there is no guidance on when to prefer jj_company_jobs for listings or jj_search_companies for discovery.

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