Skip to main content
Glama

Search Companies

search_listings
Read-only

Search remote companies by name or technologies. Filter results by tech stack to find employers that hire for your skills.

Instructions

Search for companies on Remoet. Only companies are returned (not freelance platforms or job boards). Returns a summary for each company — use get_listing with the slug to see full details (description, perks, URLs).

CRITICAL: Only star companies whose tech stack OVERLAPS with the user's skills. A JavaScript developer should NOT star a company that only uses Go, Rust, or Java. Stars are the user's noise filter — irrelevant stars pollute their job feed with jobs they can't apply to. Every star must make sense for THIS user.

Best approach: 1) Read the user's profile to understand their tech stack and experience, 2) Search listings filtering by the user's actual technologies, 3) Review results and only star companies where the tech stack genuinely matches.

SEARCH LOGIC: Relevance scoring ranks results by: exact name match (+10), name starts with query (+5), name contains query (+2), and each tech stack match (+20 per matching technology). Text search also matches description and about fields. Technologies are auto-normalized (e.g. "ts" → "TypeScript", "react" → "React"). Combine searchQuery and techStack for best results.

If the user's interests aren't clear from their profile, ask them what kind of companies they're looking for.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchQueryNoSearch keyword — matches company name, description, and about text
techStackNoFilter by technologies (e.g. ["React", "Node.js", "TypeScript"]). Technologies are auto-normalized.
sortByNoSort results by: stars (most popular), jobCount (most active hiring), or name (alphabetical). Default: stars
pageNoPage number, starting from 1 (default: 1)
pageSizeNoResults per page, max 100 (default: 20)
Behavior5/5

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

Discloses relevance scoring logic, auto-normalization of technologies, and search behavior across multiple fields. Annotations already indicate read-only and non-destructive, and description adds detailed behavioral context without contradiction.

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?

Well-structured with logical sections, but slightly verbose (e.g., repeated best approach). Every sentence adds value, but could be more concise.

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?

Comprehensive coverage: purpose, search logic, usage guidelines, critical starring note, and alternatives. No output schema, but description compensates fully for agent decision-making.

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?

Schema coverage is 100%, so baseline is 3. Description adds value by explaining techStack auto-normalization, sortBy meaning, and search behavior beyond schema descriptions.

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 it searches for companies on Remoet and distinguishes from freelance platforms or job boards. It also references siblings like get_listing for full details, establishing a unique purpose.

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

Usage Guidelines5/5

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

Provides explicit guidance: read user profile, search with technologies, review results, and star only relevant companies. Also advises asking users if interests are unclear, and contrasts with get_listing for details.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/remoet-labs/remoet-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server