Skip to main content
Glama
mohamed-ashraf-elsaed

loupe-mcp

by mohamed-ashraf-elsaed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_comments

Retrieve Loupe product-feedback comments as an actionable backlog, filtered by page, repo, branch, stage, priority, or change type, so you can prioritize urgent items.

Instructions

List Loupe product-feedback comments for the project as a task backlog. Each item carries its board stage, priority and change type, so you can start with the most urgent. Use this to see what a PM has flagged, then work through the items.

Input Schema

NameRequiredDescriptionDefault
urlNoFilter to a single page path, e.g. /checkout.
repoNoFilter to one repository, e.g. "org/repo".
branchNoFilter to one branch, e.g. "main".
statusNoFilter by stage. Omit for all.
priorityNoFilter by priority.
changeTypeNoFilter by change type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.14.1
    • addedInput schema / properties / branch
      Added value: +{
+  "description": "Filter to one branch, e.g. \"main\".",
+  "type": "string"
+}
    • addedInput schema / properties / changeType
      Added value: +{
+  "description": "Filter by change type.",
+  "type": "string"
+}
    • addedInput schema / properties / priority
      Added value: +{
+  "description": "Filter by priority.",
+  "type": "string"
+}
    • addedInput schema / properties / repo
      Added value: +{
+  "description": "Filter to one repository, e.g. \"org/repo\".",
+  "type": "string"
+}
    • changedInput schema / properties / status / description
      Previous value: -"Filter by status. Omit for all."New value: +"Filter by stage. Omit for all."
    • removedInput schema / properties / status / enum
      Removed value: -[
-  "open",
-  "in_progress",
-  "done"
-]
  2. First observedv0.5.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses what each returned item contains (board stage, priority, change type) and the intended ordering by urgency, but says nothing about read-only semantics, pagination, result limits, or sort order guarantees.

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?

Three short sentences, front-loaded with the core action and result shape. The closing "then work through the items" is mildly redundant with "start with the most urgent," but the description stays tight overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 does well to sketch the returned item fields and urgency framing. However, it leaves gaps around pagination, result volume, and sorting behavior for a six-filter listing tool.

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 filters (url, repo, branch, status, priority, changeType) are already documented in the schema. The description adds no syntax, format, or combination guidance beyond what the schema provides, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("List") and resource ("Loupe product-feedback comments") scoped to a project, and frames the return as a task backlog. It is distinguishable from the singular sibling get_comment, though it never names that sibling explicitly.

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 to see what a PM has flagged, then work through the items" gives a clear usage context and intent. It offers no explicit exclusions or named alternatives (e.g. get_comment for a single thread), so it stops short of full routing guidance.

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

Deploy Server

Other Tools