Skip to main content
Glama

SourceGeek

Count a company's open jobs

employee_company_jobs_count
Read-only

Return the total number of open job postings for a company by numeric company id.

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": {
      "companyId": "<companyId>"
    },
    "name": "employee_company_jobs_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdYesNumeric company id (e.g. '1441'). The company page lookup by vanity name or URL returns it as companyId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the useful scope qualifier that only 'open' postings are counted and that the result is a single total, which matters since there is no output schema, but it says nothing about permissions, costs, or behavior for invalid/unknown company ids.

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?

A single sentence with no filler, and the core purpose (total count of open postings) is front-loaded before the parameter constraint. Nothing is redundant or padded.

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 one-parameter read tool with no output schema, the definition conveys what is returned (a total count) and what is counted (open postings). Only edge-case behavior, such as what happens for an unknown or non-numeric id, is left unaddressed.

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 coverage is 100%, and the schema property description already explains the numeric pattern and points to the company page lookup for obtaining companyId. The description's phrase 'by numeric company id' simply restates that, adding no format or sourcing detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource: returns a total count of open job postings for a company. The word 'total number' distinguishes it in spirit from list-style siblings like employee_company_jobs, but no sibling is named, so the differentiation is implicit rather than explicit.

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?

There is no explicit when-to-use statement or exclusion, but the purpose strongly implies the case: use it when a count is wanted rather than the postings themselves. An agent can infer this, though nothing in the text routes it to an alternative tool.

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