Skip to main content
Glama
Sign In
LibreDesk MCP

LibreDesk MCP

by Passe12345
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_mentioned_conversations

Retrieve conversations where the current user or their team is mentioned in private notes, with each result pointing to the mention message UUID.

Instructions

Get Mentioned Conversations Get conversations where the current user, or a team they belong to, was mentioned in a private note. mentioned_message_uuid on each item points to the mention. Requires the conversations:read permission. GET /api/v1/conversations/mentioned Tags: Conversations

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (defaults to 1) (query parameter)
orderNoSort direction (case-insensitive). Defaults to `desc`. (query parameter)
filtersNoJSON-encoded filter. Either an array of conditions that are AND-ed, e.g. `[{"model":"conversations","field":"status_id","operator":"equals","value":"1"}]`, or a group `{"logic":"AND","rules":[...]}` with at most one level of nested groups. Operators: `equals`, `not equals`, `greater than`, `less than`, `set`, `not set`, `in`, `between`, `contains`, `ilike`, `not contains`. Filterable fields: `conversations` (status_id, priority_id, assigned_team_id, assigned_user_id, inbox_id, last_message_at, last_interaction_at, last_interaction_sender, created_at, waiting_since, next_sla_deadline_at, snoozed_until, sla_policy_id, tags), `conversation_statuses` (id, name), `users` (email, external_user_id), `inboxes` (channel). (query parameter)
order_byNoField to sort by, as `model.field`. Defaults to `conversations.last_message_at`. (query parameter)conversations.last_message_at
page_sizeNoNumber of items per page (defaults to 30, max 500) (query parameter)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does well: it discloses the required `conversations:read` permission, implies a read-only GET endpoint, and tells the agent that each item carries a `mentioned_message_uuid` pointing at the mention. It does not cover pagination limits or response shape, but those are partly in the schema.

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?

The body is three tight sentences front-loaded with the defining scope. The leading line restating the tool name is redundant, a small waste in an otherwise efficient definition.

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 five-parameter read tool with no annotations and no output schema, the description supplies the essential extras: the permission requirement and the field that identifies the mention. Only the return envelope and pagination behavior remain undocumented, which the schema largely covers.

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%, with defaults, enums, and the full filter grammar documented in the input schema. The description adds nothing about parameters, which is acceptable given the schema does the work, but earns only the baseline.

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 names a specific verb and resource plus a precise scope: conversations where the current user or their team was mentioned in a private note. That scope alone distinguishes it from siblings such as get_all_conversations and get_assigned_conversations without opening either 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?

The mention-based filter gives clear context for when this tool is the right choice rather than a general listing tool. It stops short of explicitly naming an alternative for the broader case or stating exclusions, so it lands at a solid 4 rather than 5.

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