Skip to main content
Glama

SteadyScrape Company Data

Company hiring summary

company_hiring_summary
Read-only

Hiring activity of 1-5 companies from their public career boards (Greenhouse, Lever, Ashby, Workday and more): open roles, roles posted in the last 7/30/90 days, change in open roles over time, new and closed roles, top functions, departments, locations and countries, seniority and remote mix, and the newest roles with links. Give company names, domains or career board URLs. Billed per company report returned.

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": {
      "companies": "<companies>"
    },
    "name": "company_hiring_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
companiesYes1-5 company names (Stripe), domains (datadoghq.com) or career board URLs (https://jobs.lever.co/palantir).
recent_rolesNoNewest roles to list per company (default 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=false and destructiveHint=false, so safety is covered. The description adds genuinely non-obvious behavior: results are drawn from public career boards across named ATS platforms, the batch is capped at 1-5 companies, and each company report returned is billed. It does not discuss data freshness or failure modes for unrecognized companies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It opens with the core purpose and the source scope, then lists the returned metrics, then closes with input formats and the billing caveat. The long metric enumeration is dense but each item tells the agent what question the tool can answer, so it earns its space. Slightly front-loaded toward enumeration over routing guidance.

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 carries the burden of describing returns, and it does so thoroughly by naming every metric category and noting the newest roles come with links. Combined with the billing and batch-size context, an agent knows what it will get and what it costs. Gaps remain around freshness, partial-match handling, and whether missing boards degrade results.

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 both parameters are already documented, including the 1-5 company formats and the recent_roles default of 5. The description restates the same input formats and the 1-5 bound without adding syntax rules, disambiguation behavior for ambiguous names, or interaction between the two parameters. Baseline 3 is appropriate.

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 names a specific resource (hiring activity from public career boards) and enumerates the exact outputs: open roles, 7/30/90-day postings, change over time, new/closed roles, functions, departments, locations, seniority, remote mix, and newest roles with links. That is far more specific than a tautology. It stops short of a 5 because it never positions itself against a sibling such as company_profile, leaving the agent to infer the boundary from the metric list alone.

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 implied rather than stated: the agent can infer this is the tool for workforce/hiring-signal questions, and the accepted input formats (names, domains, board URLs) are spelled out. There is no explicit when-not guidance and no named alternative for adjacent needs, so the agent must reason about fit. The billing note does give an implicit usage constraint worth respecting.

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