szum

List charts

list_charts

Read-only

Use this when the user wants to find charts in their saved library. Returns paginated metadata and URLs, not chart documents; requires authentication. Draft-only editor charts have publishedAt null, hasDraft true, and sizeBytes 0 because sizeBytes measures only the stored published document, not draft storage.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_charts"
  }
}

Input Schema

Name	Required	Description
`q`	No	Case-insensitive title substring search; trimmed and limited to 100 characters
`sort`	No	Sort by creation time (default), update time, or title A-Z
`limit`	No	Page size; defaults to 100 and has a maximum of 1000
`author`	No	An authorId from a listed chart, or "former" for charts whose author has left the workspace; omit to list every author
`cursor`	No	Opaque nextCursor from the previous page
`source`	No	Filter by one or more chart sources; omit to list all

Output Schema

Name	Required	Description
`items`	Yes
`total`	No	Exact match count, present for title searches or when explicitly requested
`workspace`	Yes	Workspace this connection saves and lists charts in
`nextCursor`	Yes	Opaque cursor for the next page, or null on the last page

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 21, 2026
- removedOutput schema / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / items / items / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / workspace / additionalProperties
```
Removed value: -false
```

Changed6 schema fields changedOct 21, 2026

addedInput schema / properties / author

Added value: +{
+  "description": "An authorId from a listed chart, or \"former\" for charts whose author has left the workspace; omit to list every author",
+  "pattern": "^[A-Za-z0-9_-]{1,64}$",
+  "type": "string"
+}

addedOutput schema / properties / items / items / properties / authorId

Added value: +{
+  "description": "User id of the person who made the chart, for the author filter; null when unknown",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / items / items / properties / authorName

Added value: +{
+  "description": "Name of the person who made the chart, or Former member when they no longer belong to the workspace",
+  "type": "string"
+}

changedOutput schema / properties / items / items / required

Previous value: -[
-  "id",
-  "source",
-  "title",
-  "createdAt",
-  "updatedAt",
-  "sizeBytes",
-  "publishedAt",
-  "imageUrl",
-  "embedUrl",
-  "documentUrl",
-  "hasDraft"
-]New value: +[
+  "id",
+  "source",
+  "title",
+  "createdAt",
+  "updatedAt",
+  "sizeBytes",
+  "publishedAt",
+  "imageUrl",
+  "embedUrl",
+  "documentUrl",
+  "hasDraft",
+  "authorId",
+  "authorName"
+]

addedOutput schema / properties / workspace

Added value: +{
+  "additionalProperties": false,
+  "description": "Workspace this connection saves and lists charts in",
+  "properties": {
+    "name": {
+      "description": "Personal, or the name of the Team workspace",
+      "type": "string"
+    }
+  },
+  "required": [
+    "name"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "items",
-  "nextCursor"
-]New value: +[
+  "items",
+  "nextCursor",
+  "workspace"
+]

Changed10 schema fields changedSep 26, 2026

removedOutput schema / properties / items / items / properties / configUrl

Removed value: -{
-  "description": "Owner-only chart-config endpoint",
-  "type": "string"
-}

addedOutput schema / properties / items / items / properties / documentUrl

Added value: +{
+  "description": "Owner-only chart-document endpoint",
+  "type": "string"
+}

changedOutput schema / properties / items / items / properties / hasDraft / description

Previous value: -"Whether an unpublished editor config exists; with sizeBytes 0 the chart is draft-only, otherwise it has unpublished edits alongside a stored published config"New value: +"Whether an unpublished editor document exists; with sizeBytes 0 the chart is draft-only, otherwise it has unpublished edits alongside a stored published document"

removedOutput schema / properties / items / items / properties / publishedAt / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / items / items / properties / publishedAt / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / items / items / properties / sizeBytes / description

Previous value: -"Compressed size of the stored published config, excluding drafts; 0 means no published config has been stored yet"New value: +"Compressed size of the stored published document, excluding drafts; 0 means no published document has been stored yet"

changedOutput schema / properties / items / items / required

Previous value: -[
-  "id",
-  "source",
-  "title",
-  "createdAt",
-  "updatedAt",
-  "sizeBytes",
-  "publishedAt",
-  "imageUrl",
-  "embedUrl",
-  "configUrl",
-  "hasDraft"
-]New value: +[
+  "id",
+  "source",
+  "title",
+  "createdAt",
+  "updatedAt",
+  "sizeBytes",
+  "publishedAt",
+  "imageUrl",
+  "embedUrl",
+  "documentUrl",
+  "hasDraft"
+]

removedOutput schema / properties / nextCursor / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / nextCursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / total / description

Previous value: -"Exact match count, present only for title searches"New value: +"Exact match count, present for title searches or when explicitly requested"

Changed2 schema fields changedJul 18, 2026
- changedOutput schema / properties / items / items / properties / id / description
```
Previous value: -"Opaque saved-chart id"New value: +"Opaque 32-character saved-chart id"
```
- addedOutput schema / properties / items / items / properties / id / pattern
```
Added value: +"^[0-9a-f]{32}$"
```

Changed2 schema fields changedJul 18, 2026

changedOutput schema / properties / items / items / properties / hasDraft / description

Previous value: -"Whether the chart has unpublished edits"New value: +"Whether an unpublished editor config exists; with sizeBytes 0 the chart is draft-only, otherwise it has unpublished edits alongside a stored published config"

changedOutput schema / properties / items / items / properties / sizeBytes / description

Previous value: -"Stored size in bytes"New value: +"Compressed size of the stored published config, excluding drafts; 0 means no published config has been stored yet"

AddedJul 18, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the readOnly/non-destructive annotations: it discloses pagination, that results are metadata plus URLs rather than content, that authentication is required, and the non-obvious draft-only quirk (publishedAt null, hasDraft true, sizeBytes 0 because sizeBytes counts only the published document). That last detail prevents a real misinterpretation.

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?

Three sentences, front-loaded with the usage trigger, then the return contract, then the draft caveat. No filler, and the ordering puts decision-relevant information first.

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 list tool with an output schema and full schema coverage, the description supplies everything the agent still needs: when to reach for it, what shape the results take, auth requirements, and the draft-record edge case. Nothing material 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 all six parameters (q, sort, limit, author, cursor, source) are already documented in the schema. The description adds only an implicit nod to pagination; it provides no syntax, defaults, or interaction details beyond the schema, 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?

States a specific verb and resource ('find charts in their saved library') and immediately clarifies the boundary: 'Returns paginated metadata and URLs, not chart documents', which cleanly separates it from get_chart_document and get_chart. An agent can pick this tool without opening the schema.

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?

'Use this when the user wants to find charts' gives a clear positive trigger, and the 'not chart documents' clause implies the handoff to the document-reading sibling. It stops short of naming the alternative tool or stating exclusions explicitly, so it is strong but not fully routing.

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

All szum 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?