Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

remote_tech_jobs_board_all_in_one

Read-onlyIdempotent

Global Remote & Tech Jobs Scraper (Salary + Apply URL): Real-time structured data extraction feed for Global Remote & Tech Jobs Scraper (Salary + Apply URL).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "remote_tech_jobs_board_all_in_one"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum number of records to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. Added

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds only the vague phrase "real-time structured data extraction feed" — no indication of update cadence, whether results are fresh scrapes or cached, rate limits, or what the feed contains. It does not contradict the annotations, but it contributes almost nothing beyond them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, but both clauses say the same thing, with the title repeated inside the body. It is concise only because it is content-poor, not because the wording is efficient.

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 scraping feed with no output schema, the description should convey source coverage, freshness, result shape, and limits. Instead it supplies none of these, leaving an agent unable to predict what the returned records look like beyond salary and apply URL.

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 coverage is 100% for the single maxResults parameter, whose default and meaning are fully documented in the schema. Per the baseline rule for high coverage, a 3 applies; the description adds no extra meaning about pagination or result caps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the tool name and title almost verbatim ("Global Remote & Tech Jobs Scraper (Salary + Apply URL)") followed by "Real-time structured data extraction feed for Global Remote & Tech Jobs Scraper (Salary + Apply URL)." The only signal beyond the name is that listings include salary and an apply URL, which is already in the title. It does not distinguish this from siblings like german_jobs_scraper or the greenhouse job radars.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no statement of what sources or regions are covered, and no routing to alternatives such as german_jobs_scraper or the Greenhouse tools. The agent must infer selection from the name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources