remoet

View Job Feed

get_starred_jobs

Read-only

Get job postings from the user's starred companies. This is the user's own curated feed. If the user has no stars, this returns nothing. In that case, use search_jobs instead: it reads the public catalogue. Supports filtering by search query, location, tech stack, remote policy, experience level, and minimum salary. Results are paginated. Same-title postings from one company are grouped into a single row: postingCount and postingLocations show how many raw postings it represents and where (boards often post one role per location). Results can be bookmarked with save_job.

A single filtered query can miss good roles; an unfiltered call returns the whole feed, paginated. The techStack filter uses OR logic: specifying ["React", "TypeScript", "Node.js"] returns jobs matching AT LEAST ONE of them (technologies are auto-normalized and matched across spelling variants), so filter by the technologies that genuinely matter and judge each job's fit from its own techStack field. Use searchQuery for role-based searches ("senior engineer", "frontend", "platform") and techStack for technology-based filtering.

OVER-CAP WARNING: if the response includes a "starsOverCap" field, the user has more starred companies than the limit allows and the surplus is scheduled for PERMANENT deletion on the given date. Proactively tell the user (count + date) and let them choose which companies to unstar down to the limit. NEVER unstar companies on the user's behalf just to get under the limit unless they explicitly ask you to.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number, starting from 1
`sortBy`	No	Sort field (default: createdAt)
`pageSize`	No	Results per page (max 50, default 20)
`salaryMin`	No	Minimum salary filter
`sortOrder`	No	Sort direction (default: desc)
`techStack`	No	Filter by technologies (e.g. ["React", "Node.js"])
`searchQuery`	No	Search keywords for job title, summary, or tech stack
`remotePolicy`	No	Filter by remote policy: "remote", "hybrid", "onsite", or "remote-restricted"
`locationQuery`	No	Filter by location or remote restrictions
`techStackMatch`	No	How techStack combines: "any" (default, at least one technology) or "all" (every technology required)
`experienceLevel`	No	Filter by experience level: "junior", "mid", or "senior"

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 24, 2026
- addedInput schema / properties / locationQuery / maxLength
```
Added value: +500
```
- 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
```
First observedSep 16, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the readOnly/destructive/openWorld annotations by disclosing result grouping semantics (postingCount/postingLocations), pagination, techStack normalization/OR logic, and a critical over-cap warning that surplus stars are scheduled for PERMANENT deletion. The prohibition against unstarring on the user's behalf is exactly the kind of behavioral guardrail annotations cannot express.

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?

Front-loaded with purpose, then usage, then a clearly flagged OVER-CAP WARNING in caps. The paragraph about filtered vs unfiltered queries is slightly meandering, but overall the definition is dense with useful content rather than padding.

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?

With 11 optional params, no output schema, and no annotations beyond the safety profile, the description carries the needed burden: it covers feed scope, empty-feed routing, filter mechanics, grouping, pagination, and a consequential over-cap deletion warning. Nothing an agent needs to call this correctly is missing.

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 the baseline is 3, but the description adds genuine meaning: it explains the OR logic of techStack, its auto-normalization across spelling variants, searchQuery vs techStack division of labor, and pagination behavior. It does not clarify sortBy or salaryMin semantics, keeping it short of 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 and resource ('Get job postings from the user's starred companies') and immediately scopes it as 'the user's own curated feed', which distinguishes it from the public-catalogue sibling search_jobs. An agent can tell it apart from search_jobs without opening a schema.

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?

Explicitly names the when-not ('If the user has no stars, this returns nothing') and the alternative to use instead ('use search_jobs instead: it reads the public catalogue'). Adds further conditional guidance on filtered vs unfiltered calls and on choosing searchQuery vs techStack, and routes saving to save_job.

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

All remoet tools Inspect

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

Need Help?