Skip to main content
Glama

Courier

by io.github.trycourier
OverviewDiscussionsAdmin

list_notifications

Read-only

List notification templates, newest first. Pass tags to return only templates carrying ALL of the given tags. Page through the rest with cursor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoOnly return templates carrying ALL of these tags, matched case-insensitively on the tag name shown in a template's tags field (e.g. ["onboarding"]). Omit to list every template.
cursorNoThis is an opaque token — never decode it, edit it, or rebuild it. Pass it back exactly as it appeared in the previous response's cursor field, byte for byte. Omit this entirely when you don't have one from a prior response of this exact call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tags
      Added value: +{
+  "description": "Only return templates carrying ALL of these tags, matched case-insensitively on the tag name shown in a template's tags field (e.g. [\"onboarding\"]). Omit to list every template.",
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Pagination cursor"New value: +"This is an opaque token — never decode it, edit it, or rebuild it. Pass it back exactly as it appeared in the previous response's cursor field, byte for byte. Omit this entirely when you don't have one from a prior response of this exact call."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark readOnlyHint=true, so the description need not repeat that this is read-only. It adds behavioral details beyond the schemas: newest-first ordering, the ALL-of-tags matching semantics, and cursor-based pagination. This gives the agent a solid picture of how the tool behaves without contradiction.

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?

The description is three short sentences, front-loaded with the core purpose in the first phrase. Every sentence adds a distinct piece of information: purpose, filtering, pagination. There is no verbose filler.

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 two-optional-parameter list tool with no output schema and minimal annotations, the description covers the main behavioral aspects: ordering, filtering, and pagination. It does not explicitly describe the response shape, but the phrase 'Page through the rest with cursor' implies the cursor is in the response, and the tool's name and purpose make the list return obvious. Overall it is sufficiently complete.

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 input schema already documents both `tags` and `cursor` thoroughly. The description essentially restates the schema's tag-filtering behavior and cursor-page concept, adding no new information. Baseline 3 applies because the schema does the heavy lifting.

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: 'List notification templates, newest first.' The resource 'notification templates' differentiates from sibling tools like list_notification_versions and list_notification_checks, which are clearly not templates. The ordering detail further clarifies the behavior.

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?

The description gives clear context that this tool lists notification templates, and explains tag filtering and cursor pagination. However, it does not explicitly direct the agent to alternatives for related resources (e.g., versions) or state when not to use this tool. That leaves the usage guidance at 'clear context, no exclusions' rather than explicit alternative routing.

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

All Courier toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources