Refine Job Search

signals.track

Start tracking a company for new job openings

Input Schema

TableJSON Schema

Name	Required	Description
`locations`	No	Locations to filter by; use "remote" for remote roles
`careers_url`	Yes	URL of the company careers page
`departments`	No	Departments to filter by
`company_name`	Yes	Name of the company
`sync_frequency`	No	How often Refine should refresh this company
`exclude_keywords`	No	Keywords to exclude
`include_keywords`	No	Keywords that must appear in the role
`seniority_levels`	No	Seniority levels to include

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`meta`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedAug 26, 2026

addedInput schema / properties / careers_url / format
```
Added value: +"uri"
```
changedOutput schema / properties / data / additionalProperties
```
Previous value: -{}New value: +false
```

removedOutput schema / properties / data / properties / notification_cadence

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Notification cadence"
-}

addedOutput schema / properties / data / properties / sync_frequency

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "How often the company is refreshed"
+}

AddedAug 23, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations indicate readOnlyHint=false and openWorldHint=true, meaning the tool has side effects and is not read-only. The description adds nothing beyond the literal 'start tracking', failing to disclose what side effects occur (e.g., background monitoring, recurring syncs) or any prerequisites (valid careers URL). With no annotation coverage for side effects, the description should carry this weight but does not.

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?

The description is a single, front-loaded sentence with no filler. It states the action and purpose in under ten words, making it extremely easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating tool with 8 parameters, 2 required, and an openWorldHint, the description is too sparse. It does not explain what happens after tracking starts, whether it is idempotent (annotation says it's not), or what the output schema represents. While an output schema exists, the description still fails to convey the operational context an agent needs to call the tool correctly and anticipate consequences.

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 every parameter (locations, departments, sync_frequency, etc.) is already documented in the schema. The description adds no parameter-specific meaning, so the baseline of 3 is appropriate given the schema's thoroughness.

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 clearly states the action ('Start tracking a company') and the purpose ('for new job openings'), making the tool's intent unambiguous. It doesn't explicitly distinguish from sibling tools like signals.update or signals.untrack, but the specific phrasing differentiates it sufficiently for a capable agent.

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 description implies the context for use: when the user wants to begin monitoring a company for openings. However, it offers no guidance on when not to use it, nor does it point to alternatives (e.g., signals.update for modifying an existing track). The context is clear but the guidance is incomplete.

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

All Refine Job Search tools Inspect

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

Need Help?