Skip to main content
Glama

remoet

by dev.remoet.api
OverviewDiscussionsAdmin

Search Companies

search_listings
Read-only

Works without a Remoet account, except starred: true. Search companies on Remoet, or list the user's starred companies (starred: true). Returns a summary per result. Full detail (description, perks, URLs) is on get_listing, by slug. Job boards and aggregators are excluded; talent networks that post direct roles (e.g. Toptal) appear as companies.

CRITICAL, star quality: only star companies whose tech stack OVERLAPS the user's skills (a JavaScript dev should not star a Go/Rust-only shop). Stars are the user's job-feed noise filter, so an irrelevant star pollutes their feed with jobs they can't use. Judge overlap by each result's matchedTechStack: the technologies from your techStack filter that the company actually uses, checked against its FULL stack (not the capped preview), so do NOT skip a company just because the visible preview omits the user's skills. An empty matchedTechStack means the result matched on text, not tags. techStackCount is the company's true tag total; the full stack unlocks on starring. techStack matches AT LEAST ONE filtered technology by default; set techStackMatch:"all" to require every one.

starred: true limits results to the user's starred companies; combined with techStack it returns matchedTechStack per starred company, which shows any star with zero overlap.

Example: search_listings({ searchQuery: "payments", techStack: ["TypeScript", "React"], experienceLevel: ["mid"] }).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, starting from 1 (default: 1). Without a Remoet account the first 10 pages are available.
sortByNoSort results by: stars (most popular), jobCount (most active hiring), or name (alphabetical). Default: relevance when searching/filtering, stars when browsing
starredNoSet true to list the user's STARRED companies instead of searching the full catalog. In this mode searchQuery/experienceLevel/sort/pagination are ignored; pass techStack to get a matchedTechStack per starred company for auditing stack fit.
pageSizeNoResults per page, max 20 without a Remoet account (default: 20)
techStackNoFilter by technologies (e.g. ["React", "Node.js", "TypeScript"]). Each result's matchedTechStack shows which matched. Technologies are auto-normalized.
searchQueryNoSearch keyword: matches company name, description, and about text
techStackMatchNoHow techStack combines: "any" (default, at least one technology) or "all" (every technology required; use for must-have stacks)
experienceLevelNoOnly companies with at least one open role at any of these seniorities (e.g. ["junior"] for entry-level-friendly companies). Each result's experienceLevels field shows its per-seniority role counts; a 0 can also mean seniority was not detected for those roles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / page / description
      Previous value: -"Page number, starting from 1 (default: 1)"New value: +"Page number, starting from 1 (default: 1). Without a Remoet account the first 10 pages are available."
    • changedInput schema / properties / page / maximum
      Previous value: -10000New value: +10
    • changedInput schema / properties / pageSize / description
      Previous value: -"Results per page, max 100 (default: 20)"New value: +"Results per page, max 20 without a Remoet account (default: 20)"
    • changedInput schema / properties / pageSize / maximum
      Previous value: -100New value: +20
  2. Changed4 schema fields changed
    • changedInput schema / properties / page / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / pageSize / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / searchQuery / maxLength
      Added value: +500
    • addedInput schema / properties / techStack / items / maxLength
      Added value: +100
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare a read-only, non-destructive, closed-world operation, and the description adds substantial extra context: account-free access limits, exclusion of job boards/aggregators, inclusion of direct-post talent networks, and the fact that the full tech stack only unlocks on starring. This is behavior well beyond what the structured fields convey.

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?

Purpose and alternatives are front-loaded, but a large block is devoted to star-quality guidance (who should be starred) that is primarily star_listing's concern rather than search invocation. The example and CRITICAL framing aid the agent but push length well past what a search call strictly needs.

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?

There is no output schema, and the description compensates by explaining return shape (a summary per result, matchedTechStack, techStackCount, experienceLevels) and the no-account paging limits. For an 8-parameter, zero-required search tool this is complete enough to call correctly.

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, but the description adds real semantics beyond the schema: matchedTechStack reflects only filtered technologies checked against the FULL stack, an empty matchedTechStack means a text-only match, techStackCount is the true tag total, and techStack defaults to at-least-one matching. It doesn't cover sortBy/pagination interplay, keeping it from a 5.

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?

States a specific verb+resource ("Search companies on Remoet") plus a second mode ("list the user's starred companies"), and explicitly points to the sibling get_listing for full detail by slug. An agent can distinguish it from search_jobs and get_listing without opening any schema.

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 clear conditions: works without a Remoet account except when starred:true, use get_listing for full detail, set techStackMatch:"all" for must-have stacks, and starred:true ignores searchQuery/experienceLevel/sort/pagination. It does not explicitly frame when to choose this over search_jobs, so it falls short of the full when/when-not/alternatives bar.

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

All remoet toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources