noticed

get_list

Read-onlyIdempotent

Open one list: relevance-ranked members, pending suggestions and rejected_person_ids. Returns canonical_url and review_url; a link does not imply reviews are configured. Use member_total for the size, never members.length. Continue while member_has_more with page/page_size. Identify by list_id or list_name.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	1-based member page; default 1.
`list_id`	No	The list's id (from list_lists / create_list). Pass this OR list_name.
`list_name`	No	The list's name, matched case-insensitively. Pass this OR list_id.
`page_size`	No	Members per page; default 25, maximum 200.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether noticed completed the operation.
`data`	No	The operation result when ok is true.
`error`	No	A human-readable error when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedSep 15, 2026

addedInput schema / properties / page

Added value: +{
+  "description": "1-based member page; default 1.",
+  "exclusiveMinimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / page_size

Added value: +{
+  "description": "Members per page; default 25, maximum 200.",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / data / properties / canonical_url
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```
addedOutput schema / properties / data / properties / member_has_more
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / data / properties / member_page
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / data / properties / member_page_size
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / data / properties / member_total
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / data / properties / rejected_person_ids

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / properties / review_url
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```

changedOutput schema / properties / data / required

Previous value: -[
-  "list_id",
-  "name",
-  "members",
-  "suggestions",
-  "pending_total"
-]New value: +[
+  "list_id",
+  "name",
+  "canonical_url",
+  "review_url",
+  "member_total",
+  "member_has_more",
+  "member_page",
+  "member_page_size",
+  "rejected_person_ids",
+  "members",
+  "suggestions",
+  "pending_total"
+]

Changed1 schema field changedAug 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "description": "The operation result when ok is true.",
+      "properties": {
+        "ai_enabled": {
+          "type": "boolean"
+        },
+        "description": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "list_id": {
+          "type": "string"
+        },
+        "member_count": {
+          "type": "number"
+        },
+        "members": {
+          "items": {
+            "additionalProperties": true,
+            "properties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "name": {
+          "type": "string"
+        },
+        "organization_id": {
+          "$ref": "#/properties/data/properties/description"
+        },
+        "pending_count": {
+          "type": "number"
+        },
+        "pending_total": {
+          "type": "number"
+        },
+        "suggestions": {
+          "$ref": "#/properties/data/properties/members"
+        }
+      },
+      "required": [
+        "list_id",
+        "name",
+        "members",
+        "suggestions",
+        "pending_total"
+      ],
+      "type": "object"
+    },
+    "error": {
+      "description": "A human-readable error when ok is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether noticed completed the operation.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

First observedAug 22, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds valuable behavioral context beyond annotations: that review_url presence doesn't guarantee reviews are configured, that member_total is the authoritative size (not members.length), and that pagination continues while member_has_more. These details help the agent interpret results correctly.

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 five short, focused sentences, each adding distinct value: purpose, return fields, size caveat, pagination, and identifier choice. It is front-loaded with the primary action and contains no filler or redundant statements.

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 read-only single-list retrieval with a full output schema, the description covers all essential calling aspects: identification method, pagination pattern, return field semantics (member_total vs members.length), and the review_url caveat. The output schema handles the return structure, so nothing needed 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 baseline is 3. The description reinforces that list_id and list_name are alternatives (already stated in schema) and that page/page_size drive pagination, but it does not introduce new parameter constraints or syntax. It adds marginal context beyond the schema, but not enough to raise the score above baseline.

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: 'Open one list' and enumerates the returned contents (relevance-ranked members, pending suggestions, rejected_person_ids). It clearly distinguishes itself from list_lists (which lists multiple lists) and from update_list/delete_list (mutating) by implying a read-only single-list operation.

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?

Provides clear guidance on how to call the tool: identify by list_id or list_name, and paginate with page/page_size while member_has_more. It also gives a caveat about using member_total for size. However, it does not explicitly contrast with sibling tools like get_list_reviews, though mentioning review_url hints at it. Overall, clear usage context without exclusions.

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

All noticed tools Inspect

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

Need Help?