Skip to main content
Glama

Reqbeat Hiring Signals

by com.reqbeat
OverviewDiscussionsAdmin

Watch a company

watch_company

Subscribe to a company's hiring events on a registered webhook -- webhook_endpoint_id must belong to the same customer as the authenticated key. Meters one watch unit.

`event_types` names which events fire it, at least one of: `opened` (a
req seen for the first time), `reobserved` (a known req seen again on a
later day), `reposted` (a req that came back after it was gone), `closed`
(a req verified gone from its source). Anything else is refused and
creates nothing: a watch on a type that never fires would be billed and
silent.

A free key holds a limited number of watches at once; the one past that
is refused with the same 402 the REST route raises, and cancelling a
watch returns the slot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYes
event_typesYes
plane_api_keyNoDeprecated: pass the key in the `X-API-Key` header. Removed in 1.2.
idempotency_keyNo
webhook_endpoint_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / plane_api_key / description
      Previous value: -"Deprecated: pass the key in the `X-API-Key` header, or omit the header for demo mode. Removed in 1.2."New value: +"Deprecated: pass the key in the `X-API-Key` header. Removed in 1.2."
  2. Changed2 schema fields changed
    • addedInput schema / properties / event_types / items / enum
      Added value: +[
+  "opened",
+  "reobserved",
+  "reposted",
+  "closed"
+]
    • addedInput schema / properties / event_types / minItems
      Added value: +1
  3. Changed1 schema field changed
    • addedInput schema / properties / plane_api_key / description
      Added value: +"Deprecated: pass the key in the `X-API-Key` header, or omit the header for demo mode. Removed in 1.2."
  4. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Rich disclosure well beyond the annotations: meters one watch unit, refuses unknown event types and creates nothing to avoid silent billing, enforces a free-key watch quota, and returns a 402 mirroring the REST route. Consistent with readOnlyHint=false and non-idempotent semantics.

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?

Front-loads the core action, then layers event semantics and error/quota behavior in three tight paragraphs. Dense but each sentence carries operational value; only the event glosses push length slightly.

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?

No output schema, but the description covers billing, validation failure, and quota/error behavior thoroughly. Minor gaps remain around success return shape and idempotency_key semantics, which an agent might want for a mutating call.

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?

With only 20% schema coverage the description must compensate, and it does for the two most important params: webhook_endpoint_id ownership constraint and full definitions of each event_types enum value (opened/reobserved/reposted/closed) not present in the schema. company_id and idempotency_key remain unexplained.

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?

States a specific verb and resource: 'Subscribe to a company's hiring events on a registered webhook.' An agent can immediately distinguish it from siblings like cancel_watch, list_watches, and register_webhook.

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?

Gives a prerequisite (webhook_endpoint_id must belong to the same customer as the authenticated key) and hints at the lifecycle by noting cancelling returns the slot, but never states explicit when-to-use/when-not conditions versus alternatives such as pre_action_brief or register_webhook. Usage is implied rather than spelled out.

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 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources