Remote Impact Jobs

Get an organization and its open roles

get_organization

Read-onlyIdempotent

Organization details (homepage, careers page) and its open roles on Remote Impact.

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": {
      "slug": "<slug>"
    },
    "name": "get_organization"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Organization slug, e.g. from a job's organization.slug

Output Schema

Name	Required	Description	Default
`jobs`	Yes
`organization`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 18, 2026

changedOutput schema / properties / jobs / items / description

Previous value: -"One verified open role"New value: +"One currently listed role with recorded evidence"

addedOutput schema / properties / jobs / items / properties / data_quality

Added value: +{
+  "description": "Evidence status for eligibility and pay; unknown values must not be inferred",
+  "type": "object"
+}

addedOutput schema / properties / jobs / items / properties / eligibility_match

Added value: +{
+  "description": "Query-specific country compatibility, not legal eligibility",
+  "type": "object"
+}

Changed2 schema fields changedOct 13, 2026

addedInput schema / properties / slug / description

Added value: +"Organization slug, e.g. from a job's organization.slug"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "jobs": {
+      "items": {
+        "description": "One verified open role",
+        "properties": {
+          "apply_url": {
+            "type": "string"
+          },
+          "description_excerpt": {
+            "type": "string"
+          },
+          "eligible_countries": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "experience_level": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "integer"
+          },
+          "job_type": {
+            "type": "string"
+          },
+          "location": {
+            "type": "string"
+          },
+          "organization": {
+            "properties": {
+              "careers_url": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "homepage_url": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "name": {
+                "type": "string"
+              },
+              "slug": {
+                "type": "string"
+              },
+              "url": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "posted_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "remote_scope": {
+            "enum": [
+              "worldwide",
+              "countries",
+              "region",
+              "unspecified"
+            ],
+            "type": "string"
+          },
+          "salary": {
+            "properties": {
+              "currency": {
+                "type": "string"
+              },
+              "max": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "min": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "period": {
+                "type": "string"
+              }
+            },
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "slug": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          },
+          "verification": {
+            "type": "object"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "organization": {
+      "oneOf": [
+        {
+          "properties": {
+            "careers_url": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "homepage_url": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "name": {
+              "type": "string"
+            },
+            "slug": {
+              "type": "string"
+            },
+            "url": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "organization",
+    "jobs"
+  ],
+  "type": "object"
+}

First observedOct 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds the payload contents (homepage, careers page, open roles), which is useful but overlaps with the output schema; it says nothing about behavior for an unknown slug.

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?

One compact sentence with the resource and its returned fields front-loaded. Nothing is wasted, though it is terse enough that a little more context could have been added without bloat.

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-only lookup with an output schema that defines the return shape, the description covers what is needed. The gap is the absence of any usage context or error behavior, which is minor given the low complexity.

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?

A single required slug parameter with 100% schema description coverage, so the schema already carries the meaning and the example format. The description adds no parameter details, which matches the baseline for a fully documented schema.

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?

Names the resource (organization) and enumerates what it returns: homepage, careers page, and open roles. A specific verb is only implied by the name 'get_organization', and the description does not distinguish it from siblings like get_job or search_jobs, but the content is clear enough to identify the tool.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives. The only routing hint ('from a job's organization.slug') lives in the schema property, not the description, so an agent must infer that this follows a get_job lookup.

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

All Remote Impact Jobs tools Inspect

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

Need Help?