Skip to main content
Glama

SourceGeek

Get a company's open jobs

employee_company_jobs
Read-only

List a company's current job postings (title, url, location, posted date, job id) by company vanity name, URL or numeric id, newest first by default. Paged; returns paging info.

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": {
      "companyUsernameOrUrl": "<companyUsernameOrUrl>"
    },
    "name": "employee_company_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based results page.
sortNoOrdering; defaults to mostRecent.
limitNoMaximum items to return (1-100, default 10). Results beyond the provider's page are not fetched.
companyUsernameOrUrlYesA company vanity name such as 'google' or a company page URL ending in /company/google.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly, openWorld, and non-destructive behavior, so the description's job is supplementary – and it delivers by disclosing default ordering, paging, that paging info is returned, and which fields come back. It stops short of covering edge cases such as an unknown company or what an out-of-range page yields.

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, both front-loaded with the highest-value information: identity and return shape first, paging second. No filler and no repetition of the title.

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 compensates by naming the returned fields, and it covers paging for a four-parameter tool whose schema is fully documented. The main remaining gap is the absence of any routing guidance among the several job-search and job-count siblings.

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%, so the baseline is 3, and the description earns an extra point by widening the accepted identifier forms to 'company vanity name, URL or numeric id' – the numeric id case is not mentioned in the schema text. It also restates the mostRecent default, which is redundant with the schema's sort description.

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 gives a specific verb and resource ('List a company's current job postings') and even enumerates the returned fields (title, url, location, posted date, job id), so the agent knows exactly what it gets. It implicitly separates itself from the search-based and count siblings by being company-scoped, but never names them, so it stops short of full 5-level differentiation.

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: the presence of a required company identifier signals 'use this when you already know the company.' There is no explicit guidance about when to prefer employee_search_jobs, fast_search_jobs, or employee_company_jobs_count instead, and no prerequisites are stated.

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