Skip to main content
Glama
Remote Tech, AI & YC Startup Jobs Radar MCP Server

Remote Tech, AI & YC Startup Jobs Radar MCP Server

search_remote_tech_jobs

Find real-time remote tech, AI, and Y Combinator startup jobs across Remotive, Arbeitnow, and Hacker News Jobs by keywords, with per-source limits.

Instructions

Search real-time remote tech, AI, and Y Combinator startup job listings across Remotive, Arbeitnow, and HackerNews Jobs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keywords": "<keywords>"
    },
    "name": "search_remote_tech_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsYesJob roles, programming languages, or skills (e.g., ['AI', 'python', 'typescript', 'fullstack'])
maxResultsPerSourceNoMaximum job postings per platform (1-15)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It reveals that this is a federated query across Remotive, Arbeitnow, and HackerNews Jobs and that results are 'real-time', but says nothing about read-only semantics, per-source failure behavior, deduplication across sources, or result ordering.

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?

A single front-loaded sentence with no filler; the resource scope and source list are packed efficiently into one clause.

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

Completeness3/5

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

For a two-parameter search tool with no output schema, the description covers what is searched and where, which is the essential core. It leaves open how multi-keyword queries combine, whether results are merged or grouped by source, and what the caller receives, which an agent would want for confident invocation.

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%, with both 'keywords' and 'maxResultsPerSource' documented in-schema including an example and a 1-15 range. The description adds no additional meaning about keyword matching (OR vs AND, substring vs exact) beyond what the schema already provides, so the baseline of 3 applies.

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?

Uses a specific verb ('Search') with a clearly scoped resource ('real-time remote tech, AI, and Y Combinator startup job listings') and names the three federated sources. No sibling tools exist to differentiate from, so the only gap is the absence of an explicit contrast that isn't needed here.

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 phrase 'remote tech, AI, and Y Combinator startup job listings' implicitly conveys when the tool is appropriate, and there are no alternatives to route away from. However, there is no explicit statement of when-not to use it, nor of prerequisites (e.g., network availability or rate limits).

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