Skip to main content
Glama

get_company_jobs

Read-onlyIdempotent

Retrieve real-time public job listings for a specific hiring company to find open roles, optionally filtered by location.

Instructions

Get real-time public job listings for a specific hiring company.

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": {
      "co": "<co>"
    },
    "name": "get_company_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
coYesHiring company name (e.g. 'Tata Consultancy Services', 'Zoho', 'Google')
locNoTarget location or city (optional)
limitNoMaximum number of company jobs to return (default 20)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.8
    • addedInput schema / properties / co / description
      Added value: +"Hiring company name (e.g. 'Tata Consultancy Services', 'Zoho', 'Google')"
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of company jobs to return (default 20)"
    • addedInput schema / properties / loc / description
      Added value: +"Target location or city (optional)"
  2. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish that the operation is read-only, idempotent, non-destructive, and open-world. The description adds useful freshness and scope context through 'real-time' and 'public,' but gives no further detail about sources, availability, or behavior when no listings are found.

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 single sentence is concise, front-loaded with the retrieval action, and contains no unnecessary wording. 'Real-time,' 'public,' and 'specific hiring company' all contribute meaningful scope.

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 simple three-parameter read operation with full annotations and an output schema, this is sufficient to understand and invoke the basic operation. Explicit sibling routing and clarification of the real-time data scope would make it more complete, but return-value documentation is unnecessary.

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%, so the schema already explains the company, location, and limit parameters. The description adds no parameter syntax or usage detail, and it does not resolve the schema's inconsistent limit default of 10 versus its textual claim of 20.

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 clearly states the action and resource: retrieving public job listings for one specific hiring company. The company-specific scope is useful, but it does not explicitly distinguish this tool from siblings such as search_jobs or get_company_profile.

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 phrase 'for a specific hiring company' implies when this tool is appropriate. However, there is no explicit guidance on when to prefer it over general job searches or company-profile tools, nor any exclusions or prerequisites.

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