Line9

List my diagrams

list_diagrams

Read-onlyIdempotent

List the diagrams published in the user's Line9 workspace(s): name, visibility, version, last update and permalink. Use it to find a diagram before get_diagram. Requires Line9 sign-in.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum rows to return (1–100; default 50).
`query`	No	Case-insensitive substring of the diagram name.

Output Schema

Name	Required	Description	Default
`svg`	No
`path`	No
`plan`	No
`error`	No
`width`	No
`config`	No
`height`	No
`source`	No
`status`	Yes
`themes`	No
`diagram`	No
`controls`	No
`diagrams`	No
`open_url`	No
`warnings`	No
`signed_in`	No
`truncated`	No
`watermark`	No
`edge_count`	No
`node_count`	No
`orientation`	No
`render_mode`	No
`stop_reason`	No
`diagram_type`	No
`engine_version`	No
`schema_version`	Yes
`fallback_reason`	No
`mermaid_version`	No
`pro_theme_refused`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 20, 2026
- addedOutput schema / properties / pro_theme_refused
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / themes
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```

Changed1 schema field changedOct 2, 2026

changedOutput schema / properties / fallback_reason / enum

Previous value: -[
-  "unsupported_diagram_kind",
-  "node_cap_exceeded"
-]New value: +[
+  "unsupported_diagram_kind",
+  "node_cap_exceeded",
+  "engine_panic"
+]

First observedSep 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a genuinely useful prerequisite the annotations cannot express: 'Requires Line9 sign-in.' It does not discuss pagination or result ordering, but the auth note is real added value for a read tool.

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?

Two tight sentences: the first states what is returned, the second states when to call it, followed by the auth prerequisite. Nothing is padded and the most important content (scope and returned fields) is front-loaded.

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?

An output schema exists, so the field list in the description is a bonus rather than a necessity, and the auth requirement is the key operational caveat. The definition is essentially complete for a two-parameter, zero-required-parameter list tool, with only minor omissions like result ordering or pagination behavior.

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% – limit (1–100, default 50) and query (case-insensitive substring of diagram name) are fully documented in the schema. The description adds no additional semantics for either parameter, 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?

Names a specific verb and resource ('List the diagrams published in the user's Line9 workspace(s)'), enumerates the returned fields, and differentiates itself from the sibling get_diagram by positioning itself as the discovery step before it. An agent can tell what this does and where it sits in the workflow 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?

Gives an explicit use case ('Use it to find a diagram before `get_diagram`'), establishing the ordering relative to a sibling. It does not address render_diagram or state when not to use this tool (e.g. when the diagram id is already known), so it falls short of full when/when-not coverage.

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

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