Skip to main content
Glama

Search alerts

search_alerts
Read-only

Searches published immigration announcements by keyword, newest first. For US (the default), USCIS newsroom alerts and Federal Register notices. Use it to find announcements about a form or topic, e.g. "I-765" or "fee". For GB, Home Office media statements and fact sheets that the Home Office in the media feed tags as immigration, matched by title. They are statements, not rule changes. GB results cover recent posts ImmigrationLayer has stored from the feed, not a full archive. Each GB item carries its feed categories and a licence attribution. Australian alerts list registered compilations of the Migration Regulations 1994, based on content from the Federal Register of Legislation, CC BY 4.0. AU titles state only the compilation number; search "compilation" to list them. Each AU item carries its start date and a licence attribution. To list everything published since a date without a keyword, use list_form_changes, which is free. Returns at most 100 matches per page. Pass next_cursor as cursor to continue until next_cursor is null. No match returns an empty list, not an error. Requires sign-in at https://immigrationlayer.com/login and an active plan. Without a plan it returns subscription_required. Limit: 30 calls per minute per account, shared by all paid tools, then rate_limited. Not legal advice. Sources: for US, USCIS newsroom alerts and Federal Register notices; for GB, the Home Office in the media blog feed (homeofficemedia.blog.gov.uk); for AU, the Federal Register of Legislation (legislation.gov.au). UK alert data contains public sector information licensed under the Open Government Licence v3.0. The top-level source URL identifies the exact aggregate query, including the page cursor; each result preserves its government URL, source, and content hash.

Input Schema

NameRequiredDescriptionDefault
queryYesKeyword matched case-insensitively anywhere in an alert's title. A form number such as "I-765" also matches alerts tagged with that form. Summaries are not searched
sinceNoISO 8601 date or date-time, e.g. "2026-08-01" or "2026-08-01T09:30:00Z"; limits results to alerts published on or after this instant. A date means midnight UTC; a date-time without an offset is UTC.
cursorNoOpaque navigation cursor from the preceding page's next_cursor. Omit for the first page.
countryNoISO 3166-1 alpha-2 country code. "US" (default), "GB" or "AU".

Output Schema

NameRequiredDescriptionDefault
dataYes
as_ofYes
source_urlYes
content_hashYes
not_legal_adviceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"ISO 3166-1 alpha-2 country code. \"US\" (default) or \"GB\"."New value: +"ISO 3166-1 alpha-2 country code. \"US\" (default), \"GB\" or \"AU\"."
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "US",
      -  "GB"
      -]New value: +[
      +  "US",
      +  "GB",
      +  "AU"
      +]
    • changedOutput schema / properties / data / properties / alerts / items / properties / attribution / description
      Previous value: -"Licence attribution for the source data. Present for GB, absent for US."New value: +"Licence attribution for the source data. Present for GB and AU, absent for US."
    • changedOutput schema / properties / data / properties / alerts / items / properties / source / enum
      Previous value: -[
      -  "uscis_newsroom",
      -  "federal_register",
      -  "home_office_media"
      -]New value: +[
      +  "uscis_newsroom",
      +  "federal_register",
      +  "home_office_media",
      +  "legislation_au"
      +]
    • addedOutput schema / properties / data / properties / alerts / items / properties / start_date
      Added value: +{
      +  "description": "The date the compilation shows the Regulations as in force from (YYYY-MM-DD). Present for AU, absent for US and GB.",
      +  "type": "string"
      +}
  2. Changed4 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "ISO 3166-1 alpha-2 country code. \"US\" (default) or \"GB\".",
      +  "enum": [
      +    "US",
      +    "GB"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / data / properties / alerts / items / properties / attribution
      Added value: +{
      +  "description": "Licence attribution for the source data. Present for GB, absent for US.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / data / properties / alerts / items / properties / categories
      Added value: +{
      +  "description": "The feed's category terms for the post. Present for GB, absent for US.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / data / properties / alerts / items / properties / source / enum
      Previous value: -[
      -  "uscis_newsroom",
      -  "federal_register"
      -]New value: +[
      +  "uscis_newsroom",
      +  "federal_register",
      +  "home_office_media"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Keyword to search for"New value: +"Keyword matched case-insensitively anywhere in an alert's title. A form number such as \"I-765\" also matches alerts tagged with that form. Summaries are not searched"
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the read-only, closed-world, non-destructive profile, and the description goes well beyond them: sign-in and active-plan requirements, subscription_required failure mode, 30 calls/minute shared rate limit with rate_limited signal, 100-match page cap with next_cursor paging, and empty list rather than error. It stops short of describing result field shape, but an output schema exists to cover that.

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?

Front-loaded and well organized by country, but bloated: the source list appears twice (inline per country and again in an explicit "Sources:" sentence), and provenance/licence paragraphs plus a disclaimer crowd out the operational content. Roughly a third of the text could be cut without losing decision-relevant information.

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?

For a multi-corpus search tool with a full output schema and complete annotations, everything an agent needs to call it correctly is present: required keyword, country behavior, pagination loop termination, auth and rate-limit failure modes, and the sibling alternative for date-only listing.

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 schema already documents all four parameters. The description still adds real semantics the schema lacks — country-dependent corpora, title-only matching for GB, the default of US, and the fact that summaries are not searched. Slight deduction because cursor/since behavior is largely left to the 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?

States a specific verb and resource (searches published immigration announcements), the ordering (newest first), and enumerates exactly what corpus is searched per country (USCIS newsroom + Federal Register; Home Office media feed; Migration Regulations compilations). An agent can distinguish this from check_form_edition or get_fee purely from the text.

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?

Gives a concrete usage example ("I-765" or "fee") and explicitly routes the no-keyword-by-date case to list_form_changes, even noting that alternative is free. It also warns that AU titles only carry compilation numbers and that searching "compilation" is the way to list them.

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.

Resources