Skip to main content
Glama

Courier

by io.github.trycourier
OverviewDiscussionsAdmin

list_lists

Read-only

List the workspace's lists. A list is an explicit, subscription-based group of users — someone is on it because they were subscribed, not because they match a rule. Optionally filter by an id pattern such as "example.list.*".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoFor fetching the next page. 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.
patternNoFilter by list id pattern, where * matches a segment — for example "example.list.*". Omit to return every list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Pagination cursor"New value: +"For fetching the next page. 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."
    • changedInput schema / properties / pattern / description
      Previous value: -"Filter pattern (e.g. 'example.list.*')"New value: +"Filter by list id pattern, where * matches a segment — for example \"example.list.*\". Omit to return every list."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read operation, so the description does not need to cover mutation risks. The description adds useful domain context about subscription-based lists and the optional pattern filter, but it does not disclose behavior such as pagination, ordering, or response shape beyond what the cursor schema already implies.

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 two concise sentences that front-load the primary action and then add only the essential conceptual distinction and filter guidance. Every sentence earns its place with no redundancy.

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 read-only listing tool with no required parameters and fully documented parameters, the description plus schema is nearly complete. It could go a step further by explicitly mentioning pagination or the returned list shape, but the rich cursor schema and the straightforward 'List...' phrasing make the tool adequately callable.

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%, and both parameters are already well documented, especially cursor with its detailed opaque-token warning. The description's pattern example adds little beyond the schema, so the baseline 3 is appropriate.

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 opens with a specific verb and resource: 'List the workspace's lists.' It then clarifies what a list is by contrasting subscription-based membership with rule-based membership, which distinguishes it from sibling tools like list_audiences or get_list.

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?

The description implies this tool is for enumerating lists, and it notes that the pattern parameter is optional, but it does not explicitly state when to prefer this over get_list, list_audiences, or other list-related siblings. The usage context is inferable but not spelled out.

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