Skip to main content
Glama

SourceGeek

Get a job's hiring team

employee_job_hiring_team
Read-only

List the hiring-team members shown on a job posting (fullName, headline, username, profile URL) by job id or job URL.

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

Input Schema

NameRequiredDescriptionDefault
jobIdNoJob id.
limitNoMaximum items to return (1-100, default 10). Results beyond the provider's page are not fetched.
jobUrlNoA /jobs/view/<id> URL.

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?

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the list reflects members 'shown on' the posting, implying it may be partial, but does not discuss visibility limits or failure behavior; the page-boundary caveat lives in the schema, not the description.

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 front-loaded sentence that packs the action, the resource, the return fields and the input keying with no filler or redundant restatement.

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 three-parameter read tool with no output schema, enumerating the returned fields compensates for the missing output schema, and the schema carries pagination and input format detail. What is missing is only edge-case behavior when both jobId and jobUrl are absent or conflicting.

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%, so the baseline is 3: jobId, jobUrl and limit are already documented. The description only reinforces the job-id-or-URL alternative and adds no format or interaction detail beyond the schema, such as what happens if both are supplied.

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 ('List') and resource ('hiring-team members shown on a job posting') and enumerates the returned fields, so an agent immediately knows this is not general job detail retrieval. It stops short of naming a sibling tool or explicitly contrasting with employee_job_details.

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 'by job id or job URL' implies the two accepted entry points, but there is no explicit when-to-use guidance, no exclusion of alternatives, and no note about when this is preferable to fetching full job details.

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