Skip to main content
Glama
Sign In

Remotive

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search

search
Read-onlyIdempotent

Search Remotive's curated remote-only job board by free-text query, category slug, and/or company name. Returns job listings with title, company, location tags, salary range, job type, and apply URL.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "search": "Python backend engineer"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax jobs returned (default 25)
searchNoFree-text — title / description
categoryNoCategory slug (e.g. "software-dev", "design")
company_nameNoFilter to a specific company

Output Schema

NameRequiredDescriptionDefault
jobsNoArray of remote job listings
countNoTotal number of jobs found

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "search": "Python backend engineer"
+  },
+  {
+    "category": "software-dev",
+    "company_name": "GitLab",
+    "limit": 10,
+    "search": "React"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Total number of jobs found",
+      "type": "number"
+    },
+    "jobs": {
+      "description": "Array of remote job listings",
+      "items": {
+        "properties": {
+          "category": {
+            "description": "Job category slug",
+            "type": "string"
+          },
+          "company_logo": {
+            "description": "Company logo URL",
+            "type": "string"
+          },
+          "company_name": {
+            "description": "Company name",
+            "type": "string"
+          },
+          "description": {
+            "description": "Job description",
+            "type": "string"
+          },
+          "id": {
+            "description": "Job ID",
+            "type": "number"
+          },
+          "publication_date": {
+            "description": "Publication date ISO format",
+            "type": "string"
+          },
+          "salary": {
+            "description": "Salary range if available",
+            "type": "string"
+          },
+          "title": {
+            "description": "Job title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Job listing URL",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds contextual details such as 'curated remote-only' and specifies the return fields (title, company, location tags, salary range, job type, apply URL), which goes beyond the schema. No contradictions found.

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?

The description is a single, concise sentence followed by a brief list of return fields. It is well-structured, front-loaded with the core purpose, and contains no redundant information.

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?

Given the rich annotations, complete schema (100% coverage), presence of an output schema, and manageable complexity (4 optional params), the description fully satisfies the tool's contextual needs. It covers the purpose, query options, and expected output without over-explaining.

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?

The input schema covers all four parameters with clear descriptions (e.g., 'Free-text — title / description', 'Category slug'). The tool description adds minimal additional meaning beyond the schema, so the baseline score of 3 for high schema coverage is appropriate.

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 clearly states the tool's function: searching Remotive's curated remote-only job board using free-text, category slug, or company name. It uses a specific verb ('Search') and a distinct resource ('Remotive's curated remote-only job board'), which differentiates it from sibling tools like list_categories or get_company.

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 description provides clear context for when to use the tool (searching jobs by various criteria) and mentions the supported query types. However, it does not explicitly name alternatives or state when not to use this tool, such as contrasting with search_within or other similar siblings, so it falls short of a 5.

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

All Remotive toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources