Skip to main content
Glama

List Shopify Alerts

shopify_alerts_list
Read-onlyIdempotent

Lists an app's OPEN Shopify API-deprecation alerts: breaking changes from Shopify's changelog that were matched against this app's connected repository and still need action (relevant, not ruled out by verification, and not yet acknowledged). Each alert has an alert_id, the underlying changelog entry's title/summary/url/ severity/action_required/migration_deadline/affected_apis/ recommendation, the matched code_references, and has_fix_suggestion (whether a stored AI fix already exists: fetch it with shopify_alert_get). Takes the app_id returned by apps_list. Optional limit caps the result. Requires the shopify_alerts.view permission on the app. Never triggers a new scan or fix generation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "app_id": "<app_id>"
    },
    "name": "shopify_alerts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many alerts to return in one call.
app_idYesThe app this call works on: its `app_id` uuid from `apps_list`.
organization_idNoAn organisation uuid or slug. When supplied, `app_id` is resolved within that organisation and may be a slug instead of a uuid, mirroring the Meridian web app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / app_id / description
      Previous value: -"The app uuid returned by `apps_list`."New value: +"The app this call works on: its `app_id` uuid from `apps_list`."
    • addedInput schema / properties / limit / default
      Added value: +20
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of alerts to return. Default 20, maximum 100."New value: +"How many alerts to return in one call."
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that only OPEN alerts are returned and spells out the filtering logic: relevant, not ruled out by verification, and not yet acknowledged. It also adds the required permission and the important negative behavior that it will not trigger a new scan or fix generation.

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?

The description is front-loaded with the key verb and scope, then supplies the returned fields, permission, and side-effect exclusions. It is dense and mostly earns its length, though the enumeration of alert fields is slightly verbose even though it compensates for the absence of an output schema.

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?

Because there is no output schema, the description appropriately documents the alert fields, the meaning of `has_fix_suggestion`, and how to retrieve the stored fix. It also covers the required permission, optional limit, and the fact that the call is read-only in effect. Nothing essential for correct invocation is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already explains all three parameters. The description adds useful context for `app_id` (returned by `apps_list`) and `limit` (caps the result), but it does not add meaning for `organization_id` beyond what the schema states, so the baseline 3 applies.

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?

The description states a specific verb and resource: it lists OPEN Shopify API-deprecation alerts for an app. It defines the eligibility criteria precisely (relevant, not ruled out by verification, not acknowledged) and distinguishes the output from `shopify_alert_get`, which fetches a stored fix.

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?

It says to supply the `app_id` returned by `apps_list`, notes the required `shopify_alerts.view` permission, and explicitly says it never triggers a new scan or fix generation. The main gap is that it does not explicitly contrast when to use this versus other alert-adjacent tools beyond pointing to `shopify_alert_get` for fetching a fix.

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