Skip to main content
Glama

View Job Feed

get_starred_jobs
Read-only

Retrieve job postings from your starred companies. Filter by search query, location, tech stack, remote policy, experience level, and minimum salary.

Instructions

Get job postings from your starred companies. This is the user's main job feed — if the user has no stars, this returns nothing. Quality depends on starring the RIGHT companies (ones whose tech stack matches the user's skills). If results are empty or poor, check get_starred_listings and suggest better stars. Starring is free so they can star more companies to improve their feed. Supports filtering by search query, location, tech stack, remote policy, experience level, and minimum salary. Results are paginated. Use save_job to bookmark good matches so the user doesn't lose them.

SEARCH STRATEGY: For job recommendations, run multiple searches and merge results: first a broad search (no filters) to see what's available, then targeted searches by the user's top 1-2 technologies. This ensures comprehensive coverage — a single filtered query can miss good roles. The techStack filter uses AND logic — specifying ["React", "TypeScript", "Node.js"] only returns jobs matching ALL three, so start with 1-2 core technologies, not the user's entire stack. If results are sparse, drop filters one at a time. Use searchQuery for role-based searches ("senior engineer", "frontend", "platform") and techStack for technology-based filtering.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchQueryNoSearch keywords for job title, summary, or tech stack
locationQueryNoFilter by location or remote restrictions
techStackNoFilter by technologies (e.g. ["React", "Node.js"])
remotePolicyNoFilter by remote policy: "remote", "hybrid", "onsite", or "remote-restricted"
experienceLevelNoFilter by experience level: "junior", "mid", or "senior"
salaryMinNoMinimum salary filter
sortByNoSort field (default: createdAt)
sortOrderNoSort direction (default: desc)
pageNoPage number, starting from 1
pageSizeNoResults per page (max 50, default 20)
Behavior5/5

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

Clearly explains it returns nothing without stars, results depend on star quality, supports filtering and pagination. No contradiction with annotations (readOnlyHint=true).

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 key info front-loaded, but somewhat verbose. However, every sentence adds value; no redundancy.

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?

Completely covers return behavior, filtering nuances, and provides actionable guidance for poor results. No output schema needed due to thorough description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds significant value beyond schema descriptions, e.g., explaining techStack uses AND logic, recommending starting with 1-2 technologies, and search strategy for each parameter.

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?

Explicitly states the tool retrieves job postings from starred companies, calling it the 'main job feed'. It distinguishes from siblings like get_starred_listings by advising to check that tool if results are empty.

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 extensive guidance: when to use (main feed), what to do if empty/poor (check stars, suggest better stars), and detailed search strategy including recommended filter usage.

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