Skip to main content
Glama

Job Alerts: internships and new-grad roles

Recent changes

recent_changes
Read-onlyIdempotent

Feed of role.created (announced) and role.closed events, oldest first after the given event id. Without after, returns the latest events. Pass next_after back as after to poll. Requires an API key on the Realtime plan.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recent_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoEvent id to read after: next_after from the previous call.
groupNoCompany group slugs from list_groups, any of them; an array or a comma-separated string. REST: group.
levelNoOmit for both. REST: level.
limitNoDefault 50.
queryNoText the role title or company name contains, matched as one phrase. REST: q.
sinceNoOnly roles posted within this window. REST: since.
trackNoAny of these tracks, as an array or a comma-separated string. "swe" covers frontend, backend and fullstack. REST: track.
typesNorole.created, role.closed, or both (the default); an array or a comma-separated string.
degreeNoKeep roles open to this degree program: a posting that names the degrees it accepts must include it; one naming none stays in. REST: degree.
companyNoExact company name as list_companies returns it. REST: company.
countryNoISO 3166-1 alpha-2 codes, an array or a comma-separated string. Setting it replaces the US-only default. REST: country.
us_onlyNoDefault true: roles open to US applicants. false lifts it. REST: us=0.
undergradNotrue hides roles that accept only graduate degrees. REST: undergrad=1, or degree=bachelors.
workplaceNoWorkplace types, any of them; an array or a comma-separated string. REST: workplace.
citizenshipNo"not_required" hides roles whose posting requires US citizenship or US-person status (eligibility.citizenship_required true). Roles not read yet stay in. With include_clearance=true it keeps clearance roles that state no citizenship requirement. REST: citizenship.
sponsorshipNoFor an applicant who needs visa sponsorship. "needed" hides roles whose posting says no sponsorship; roles that do not say, or are not read yet, stay in. "available" keeps only roles whose posting says it sponsors. REST: sponsorship.
graduation_yearNoHide roles whose graduation window excludes this year. REST: grad.
exclude_companiesNoCompany names to leave out; an array or a comma-separated string. REST: exclude.
include_clearanceNoDefault false hides roles requiring US citizenship, US-person status or a clearance. REST: clearance=1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / degree
      Added value: +{
      +  "description": "Keep roles open to this degree program: a posting that names the degrees it accepts must include it; one naming none stays in. REST: degree.",
      +  "enum": [
      +    "bachelors",
      +    "masters",
      +    "phd"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / undergrad / description
      Previous value: -"true hides roles that accept only graduate degrees. REST: undergrad=1."New value: +"true hides roles that accept only graduate degrees. REST: undergrad=1, or degree=bachelors."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds meaningful operational context: event ordering, cursor polling, latest-events default, and the API key/Realtime plan requirement. It does not discuss rate limits or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the feed purpose and followed by polling and auth requirements. Every sentence carries useful information with no repetition.

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 19-parameter feed with no output schema, the description covers the essential contract: event types, ordering, polling with next_after, default behavior, and auth. Return payload details and a filter overview are omitted, but the schema is highly detailed and annotations cover safety.

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. The description adds cursor-loop meaning for after beyond the schema's short note, including ordering and the no-after default; the other 18 filters are left to the already detailed schema.

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?

Names the exact resource (role.created and role.closed events) and core behavior (feed, oldest first, latest without after). The event-feed purpose is clearly distinguishable from sibling search/list tools even though no sibling is named.

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

Usage Guidelines3/5

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

Explains the polling loop by telling the agent to pass next_after back as after, and states what happens when after is omitted. It does not say when to use this instead of search_roles or other siblings, nor does it give explicit exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.