Reqbeat Hiring Signals

register_webhook

Register the delivery target a watch fires to, and get back the webhook_endpoint_id watch_company needs -- call this first if you do not already hold one. Idempotent: registering the same url twice returns the same id, so retrying is safe and never leaves you with two endpoints. secret is optional; supply one to verify the X-Plane-Signature on delivered payloads, omit it and one is generated (it is never returned). Registration itself is free -- the watch_company call that follows is what bills.

Plane session only: `webhook_endpoints` is plane-owned and this tool reads
no corpus table.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`secret`	No
`plane_api_key`	No

TDQS

A4.3/5.0

Behavior5/5

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

With no annotations, the description fully covers behavioral traits: idempotency (retry safe), secret handling (optional, generated if omitted, never returned), billing (free registration), session scope (plane-owned, no corpus table read), and return value (webhook_endpoint_id). No contradictions present.

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?

The description is a single coherent paragraph with valuable information. Each sentence contributes to understanding, though it could be slightly more concise. It is front-loaded with the core purpose.

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?

The description covers the tool's purpose, workflow relative to siblings, idempotency, secret behavior, billing, and session scope. The only missing piece is the plane_api_key parameter. No output schema, but the returned value is mentioned.

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 0%. The description adds meaning for url (idempotent on same url) and secret (optional, for signature verification, auto-generated if omitted, never returned). However, plane_api_key is not mentioned at all, so not all parameters are sufficiently explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: registering a delivery target (webhook) for a watch and returning a webhook_endpoint_id needed by watch_company. It uses specific verbs (register) and resource (delivery target), and distinguishes from sibling tool watch_company by noting this is a prerequisite.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'call this first if you do not already hold one' and explains that registration is free while the subsequent watch_company call bills. This provides context for when to use it relative to siblings, though it does not mention when not to use or alternatives for other tools.

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

All Reqbeat Hiring Signals tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.6/5.0

Disambiguation2/5

Multiple tools have overlapping purposes (e.g., get_changes/get_open_reqs/get_role all retrieve job-related data with pagination; hiring_pulse and pre_action_brief share nearly identical descriptions; is_hiring and hiring_pulse both assess company hiring status). The long, verbose descriptions provide some subtle differentiators but the functional boundaries are unclear.

Naming Consistency1/5

Naming patterns are highly inconsistent: some tools use 'get_' prefixes (get_changes, get_open_reqs, get_role), others are noun phrases (hiring_pulse, is_hiring, pre_action_brief) or verb phrases (register_webhook, watch_company, write_outcome). There is no uniform verb-object or resource-based convention, making it hard to predict functionality from names.

Tool Count3/5

The server has 11 tools, which falls within the typical 3-15 range for a domain-specific API. However, several tools appear to serve redundant or narrowly-overlapping purposes (e.g., at least five tools deal with fetching job/company data), suggesting the count could be pruned without losing core functionality.

Completeness3/5

The tool set covers core operations like searching jobs, retrieving role details, checking hiring status, registering webhooks, and writing outcomes. However, there are notable gaps: no webhook management (e.g., list/unregister), no explicit company profile retrieval, and no update/delete operations. This makes the surface feel incomplete for a comprehensive hiring-signals API.

Resources

Need Help?