Skip to main content
Glama

Remotejobify

Search

search
Read-onlyIdempotent

Search Remotejobify’s open remote jobs. Put the country the person lives in into the query ("customer support jobs in the Philippines"): most remote jobs are only open to some countries. Returns ids for fetch.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to search for.

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add domain behavior — and it does: results are ids only, not full records, and most listings are country-restricted. Pagination and result-limit behavior remain undisclosed.

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?

Three short sentences, front-loaded with purpose, then the critical query-construction tip, then the return contract. Nothing is redundant and the parenthetical example is compact and instructive.

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?

For a single-parameter read tool with full schema coverage, an output schema, and complete annotations, the description covers purpose, query construction, and the hand-off to `fetch`. Minor gaps remain around result volume and whether multiple countries can be combined in one query.

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?

The schema documents the single `query` parameter at 100% coverage, but the description adds real semantics beyond "What to search for": it specifies that the country belongs inside the free-text query and supplies an example phrasing that the schema does not.

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?

States a specific verb and resource ("Search Remotejobify's open remote jobs") and specifies the scope as open remote jobs. It routes onward to `fetch`, but does not differentiate itself from the sibling `search_jobs`, so an agent can't fully separate the two from the description alone.

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 concrete instructions on how to phrase the query — include the country the person lives in, with a worked example — and explains that results are ids meant for `fetch`, establishing the search-then-fetch workflow. It stops short of saying when to prefer `search_jobs` or `get_job` instead.

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