longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

List Sharelists

sharelist_list

Read-onlyIdempotent

List your own and subscribed community sharelists to view curated stock collections. Specify count to limit results.

Instructions

List user's own and subscribed community sharelists.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`_jq`	No	Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data \| map({symbol}). Omit for the full response.
`count`	No	Number of lists to return (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.12.0Sep 23, 2026

addedInput schema / properties / _jq / description

Added value: +"Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response."

removedInput schema / properties / count / format
```
Removed value: -"uint32"
```

Changed2 schema fields changedv0.10.6Sep 10, 2026

addedInput schema / properties / _jq
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / (root)

Previous value: -{
-  "$defs": {
-    "SharelistSummary": {
-      "properties": {
-        "creator": {},
-        "description": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "follower_count": {
-          "format": "int64",
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "is_owner": {
-          "type": [
-            "boolean",
-            "null"
-          ]
-        },
-        "name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "symbol_count": {
-          "format": "int64",
-          "type": [
-            "integer",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "lists": {
-      "items": {
-        "$ref": "#/$defs/SharelistSummary"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedv0.8.7Aug 19, 2026
- addedOutput schema / $defs / SharelistSummary / properties / description
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"SharelistCountParam"
```
Changed12 schema fields changedv0.6.0Jun 26, 2026
- removedOutput schema / $defs / SharelistSummary / description
```
Removed value: -"A single sharelist summary entry. Subset of upstream fields."
```
- removedOutput schema / $defs / SharelistSummary / properties / creator / description
```
Removed value: -"Creator info (`sharelist_popular` only); passthrough, shape\nupstream-defined."
```
- removedOutput schema / $defs / SharelistSummary / properties / description
```
Removed value: -{
-  "description": "List description.",
-  "type": [
-    "string",
-    "null"
-  ]
-}
```
- removedOutput schema / $defs / SharelistSummary / properties / follower_count / description
```
Removed value: -"Number of followers / subscribers of this list."
```
- removedOutput schema / $defs / SharelistSummary / properties / id / description
```
Removed value: -"Sharelist ID."
```
- removedOutput schema / $defs / SharelistSummary / properties / is_owner / description
```
Removed value: -"Whether the current user owns this list (`sharelist_list` only)."
```
- removedOutput schema / $defs / SharelistSummary / properties / name / description
```
Removed value: -"List name."
```
- removedOutput schema / $defs / SharelistSummary / properties / symbol_count / description
```
Removed value: -"Number of securities in the list."
```
- removedOutput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```
- removedOutput schema / description
```
Removed value: -"Returned by `sharelist_list` and `sharelist_popular`. Documented portion is\n`lists[]`."
```
- removedOutput schema / properties / lists / description
```
Removed value: -"Sharelist summaries."
```
- removedOutput schema / title
```
Removed value: -"SharelistListResponse"
```

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "SharelistSummary": {
+      "description": "A single sharelist summary entry. Subset of upstream fields.",
+      "properties": {
+        "creator": {
+          "description": "Creator info (`sharelist_popular` only); passthrough, shape\nupstream-defined."
+        },
+        "description": {
+          "description": "List description.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "follower_count": {
+          "description": "Number of followers / subscribers of this list.",
+          "format": "int64",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "id": {
+          "description": "Sharelist ID.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "is_owner": {
+          "description": "Whether the current user owns this list (`sharelist_list` only).",
+          "type": [
+            "boolean",
+            "null"
+          ]
+        },
+        "name": {
+          "description": "List name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "symbol_count": {
+          "description": "Number of securities in the list.",
+          "format": "int64",
+          "type": [
+            "integer",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `sharelist_list` and `sharelist_popular`. Documented portion is\n`lists[]`.",
+  "properties": {
+    "lists": {
+      "description": "Sharelist summaries.",
+      "items": {
+        "$ref": "#/$defs/SharelistSummary"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "SharelistListResponse",
+  "type": "object"
+}

Addedv0.4.5May 28, 2026
Removedv0.4.0May 21, 2026
Addedv0.3.2May 19, 2026
Removedv0.3.1May 15, 2026
First observedv0.1.12May 8, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, fully covering the safety profile. The description adds value by specifying that both own and subscribed community sharelists are returned, which is more than the tool name implies. It does not mention pagination behavior, sort order, or whether the response contains full list details, but those are minor gaps given the simple read-only nature.

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 single-sentence description is concise and front-loaded with the key purpose. Every word earns its place, and there is no redundant restating of the tool name or title. This is efficient and easy to parse.

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 simple two-parameter read-only list operation, the description plus annotations and schema cover the essential usage context. It does not describe return values or ordering, but no output schema exists and the tool is straightforward. A short mention of the default count behavior would push it to 5, but the current information is sufficient for safe invocation.

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 (count and _jq) are documented in the input schema. The description does not add parameter-level detail beyond the schema, which is acceptable because the schema carries the full burden. Baseline score of 3 is appropriate when the schema fully explains parameters.

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 ('List') and resource ('user's own and subscribed community sharelists'), which immediately distinguishes it from sibling tools like sharelist_detail, sharelist_popular, and sharelist_add. This is clear and unambiguous about what is being enumerated.

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 makes it clear this tool is for enumerating the user's own and subscribed sharelists, which provides clear context for when to use it. It does not explicitly name alternatives or exclusion conditions, but the scope is well implied by contrasting with sharelist_detail and sharelist_popular. No alternative routing is provided, but the primary use case is evident.

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

Deploy Server

List Sharelists

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools