Laraue Boards

list_issues

Lists issues in the caller's organization, optionally filtered by space, epic id, status id, status category id, or assignee id. Returns up to 50 per page, most recently updated first - check hasNextPage for more. Each issue has a title, and its canEdit/canDelete reflect the caller's actual permissions on it, statusCategory/statusCategoryId tell what its status means (Created, InProgress or Completed), and url is its page in the web app.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Zero-based page number - pass the previous result's page + 1 for the next page. Omit for the first page.
`count`	No	Max issues per page, 1-50. Omit for the default of 50.
`epicId`	No	Only issues in this epic id, from list_epics. Omit to include every epic.
`spaceKey`	No	Only issues in this space (e.g. 'BRD'), from list_spaces. Omit to search every space.
`statusId`	No	Only issues with this exact status id, from list_statuses. Omit to include every status.
`assigneeId`	No	Only issues assigned to this user id, from list_members. Omit to include every assignee.
`statusCategoryId`	No	Only issues whose status has this category id, from list_statuses' categoryId: 0 = Created (not started), 1 = InProgress, 2 = Completed (finished). Works across epics whatever their statuses are named. Omit to include every category.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

addedInput schema / properties / statusCategoryId

Added value: +{
+  "default": null,
+  "description": "Only issues whose status has this category id, from list_statuses' categoryId: 0 = Created (not started), 1 = InProgress, 2 = Completed (finished). Works across epics whatever their statuses are named. Omit to include every category.",
+  "type": [
+    "integer",
+    "null"
+  ]
+}

Changed1 schema field changedSep 28, 2026

addedInput schema / properties / epicId

Added value: +{
+  "default": null,
+  "description": "Only issues in this epic id, from list_epics. Omit to include every epic.",
+  "type": [
+    "integer",
+    "null"
+  ]
+}

Changed2 schema fields changedSep 23, 2026

changedInput schema / properties / count / description

Previous value: -"Max issues to return per page, 1-50. Omit for the default of 50."New value: +"Max issues per page, 1-50. Omit for the default of 50."

changedInput schema / properties / page / description

Previous value: -"Zero-based page number. Omit or pass 0 for the first page; pass the previous result's page + 1 to get the next page."New value: +"Zero-based page number - pass the previous result's page + 1 for the next page. Omit for the first page."

Changed5 schema fields changedSep 23, 2026

addedInput schema / properties / assigneeId

Added value: +{
+  "default": null,
+  "description": "Only issues assigned to this user id, from list_members. Omit to include every assignee.",
+  "format": "uuid",
+  "type": [
+    "string",
+    "null"
+  ]
+}

removedInput schema / properties / assigneeName

Removed value: -{
-  "default": null,
-  "description": "Only issues assigned to a user whose display name contains this text. Omit to include every assignee.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

changedInput schema / properties / spaceKey / description

Previous value: -"Only issues in this space (e.g. 'BRD'). Omit to search every space."New value: +"Only issues in this space (e.g. 'BRD'), from list_spaces. Omit to search every space."

addedInput schema / properties / statusId

Added value: +{
+  "default": null,
+  "description": "Only issues with this exact status id, from list_statuses. Omit to include every status.",
+  "type": [
+    "integer",
+    "null"
+  ]
+}

removedInput schema / properties / statusName

Removed value: -{
-  "default": null,
-  "description": "Only issues with this exact status name (e.g. 'In Progress'). Omit to include every status.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

First observedSep 22, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses page size (up to 50), sort order (most recently updated first), pagination via hasNextPage, and that canEdit/canDelete reflect the caller's real permissions. It omits obvious caveats like read-only nature and any scoping/auth limits, but the behavioral disclosure is substantially richer than typical.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then pagination, then return-field semantics in a logical flow. The third sentence enumerating return fields is dense but earns its place given no output schema; overall efficient with minimal waste.

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?

With no output schema and no annotations, the description compensates by describing the return payload (title, canEdit/canDelete, statusCategory/statusCategoryId, url) and pagination signals. Combined with the fully documented input schema, an agent has everything needed to call and interpret results.

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 schema already documents all seven parameters in detail (page, count, epicId, spaceKey, statusId, assigneeId, statusCategoryId). The description merely summarizes the filterable dimensions, adding little beyond what the schema provides, 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?

The description uses a specific verb and resource ('Lists issues in the caller's organization') and immediately scopes it with the available filters. An agent can distinguish this from siblings like list_epics, list_spaces, and get_issue without opening any schema.

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?

Usage is implied: the filter parameters reference list_epics, list_spaces, list_statuses, and list_members, hinting at a workflow, and the pagination note implies iteration. But there is no explicit statement of when to use this versus get_issue or the other list_* tools, and no exclusions.

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

All Laraue Boards tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

list_issues

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources