Refine Job Search

signals.update

Idempotent

Update filters on a tracked company

Input Schema

TableJSON Schema

Name	Required	Description
`locations`	No	Locations to filter by; use "remote" for remote roles
`signal_id`	Yes	Signal (tracked company) id
`departments`	No	Departments to filter by
`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.

Changed3 schema fields changedAug 26, 2026

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

A4.2/5.0

Behavior4/5

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

The description discloses the mutation target (filters) and the state requirement (already tracked), which is useful beyond the annotations. It does not clarify whether the update merges or replaces existing filters, nor that sync_frequency is also updatable, but it is consistent with the idempotentHint and destructiveHint annotations.

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?

One short, front-loaded sentence with no filler. It conveys the essential operation and condition without redundancy.

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?

Given the rich schema, output schema, and annotations, the description is mostly sufficient for tool selection and invocation. The main missing piece is update semantics for omitted filter parameters; otherwise the noun/verb pair is adequate.

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?

All seven parameters already have descriptions in the schema, so the description does not need to repeat them. It adds no extra semantic detail about formats, defaults, or how omitted parameters behave.

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 pairs a specific verb ('Update') with a concrete resource ('filters on a tracked company'), and the 'tracked company' qualifier separates it from siblings like signals.track, signals.pause, and signals.resume. It is clear without needing to open the schema.

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?

The phrase 'on a tracked company' implies the signal must already exist and that this tool modifies an existing tracker rather than creating one. It does not explicitly name alternatives such as signals.track for creation or signals.pause/resume for status changes, so it stops short of full when-to-use guidance.

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

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.

Resources

Need Help?