Skip to main content
Glama
Sign In
freehire

freehire

by strelov1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

subscribe

Create a saved job alert using any search filters; new matching postings go to your connected email, Telegram, app, or webhook channels.

Instructions

Create a job alert: a saved search over ANY of the job search's filters whose new postings are delivered to the person on the channels their account has connected (email, Telegram, the mobile app, a webhook) — this conversation is not notified. e.g. remote senior Go roles in the EU paying at least 80k EUR is {"filters":{"work_mode":["remote"],"seniority":["senior"],"skills":["go"],"regions":["eu"],"salary_currency":["EUR"]},"salary_min":80000}. Run the same search with search first so the person sees what they will get. The search must narrow the catalogue. Values not in a filter's vocabulary are dropped and named in ignored_params. Leave channels empty for the default (email when alert mail is on, otherwise the first connected channel). The answer's alert.id addresses the alert from then on. Saves the search on the account (or reuses the one already selecting the same postings); nothing existing is changed.

Input Schema

NameRequiredDescriptionDefault
nameNoA name for the alert (1-100 characters). Omit to name it from its filters.
queryNoFree-text query, with the job search's operators.
filtersNoFacet filters by param name (skills, seniority, category, work_mode, regions, countries, cities, metros, company_slug, employment_type, salary_currency, source, …), each a list of values. An unknown filter name is refused.
channelsNoWhere to deliver. Only a channel the account has connected is accepted.
salary_maxNoOnly postings whose stated salary ceiling is at most this. 0 clears it on update.
salary_minNoOnly postings whose stated salary floor is at least this, in the posting's currency — pair it with filters.salary_currency. 0 clears it on update.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.0

TDQS

A4.6/5.0
Behavior5/5

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

With only readOnlyHint=false available, the description carries the behavioral load and does it well: delivery goes to the account's connected channels and "this conversation is not notified", invalid vocabulary values are silently dropped and surfaced in `ignored_params`, empty channels fall back to a defined default, and existing alerts are never mutated. These are non-obvious side effects an agent could not infer from annotations or schema.

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-loaded with the definition before the workflow and the example, and nearly every sentence adds a distinct fact. Some clauses are dense and clause-stacked ("delivered to the person on the channels their account has connected..."), which costs a bit of readability without adding padding.

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

Completeness5/5

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

For a 6-param mutation tool with a nested object and no output schema, the description still covers return handling ("The answer's alert.id addresses the alert from then on"), validation feedback, defaults, and idempotency. An agent has everything needed to call it correctly on the first try.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: a worked JSON example of the nested `filters` object, the default-resolution rule for empty `channels`, the currency pairing for `salary_min`, and the derivation rule for `name`. Only `salary_max` and `query` are left entirely to the schema.

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?

Opens with a specific verb and resource ("Create a job alert: a saved search over ANY of the job search's filters") and immediately defines the resource in terms of the sibling concept `search`. An agent can distinguish this from `update_subscription`, `list_subscriptions`, and `unsubscribe` without opening any 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?

Gives a concrete pre-call workflow ("Run the same search with `search` first so the person sees what they will get") and a validity constraint ("The search must narrow the catalogue"). It also implies create-only semantics ("reuses the one already selecting the same postings; nothing existing is changed"), though it never explicitly names `update_subscription` as the path for modifying an existing alert.

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

Deploy Server

Other Tools