Skip to main content
Glama

List conversations by sentiment

list_sentiment_conversations
Read-onlyIdempotent

List conversations by sentiment. The conversations behind a cell of the sentiment report: filter by opening and closing sentiment, a risk flag, worst frustration, who handled it, an agent, an inbox or a team. Same range rules as the report; at most 50, latest first. Administrators only. Requires feature: ai_decisions.

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_sentiment_conversations"
  }
}

Input Schema

NameRequiredDescriptionDefault
flagNoOnly conversations with this flag raised.
sinceNoUnix timestamp where the range starts.
untilNoUnix timestamp where the range ends.
fieldsNoOptional: return only these fields of each record.
channelNo`voice` keeps only phone calls to AI lines, `chat` everything else. Omit for both.
closingNoClosing (latest) sentiment.
handlerNoWho handled it at the last burst.
openingNoOpening sentiment. With `closing`, only conversations read at least twice.
team_idNo
inbox_idNo
assignee_idNoThe agent handling it at the last burst.
frustrationNoWorst frustration reached.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / channel
      Added value: +{
      +  "description": "`voice` keeps only phone calls to AI lines, `chat` everything else. Omit for both.",
      +  "enum": [
      +    "chat",
      +    "voice"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description adds real behavioral facts: administrator-only access, a required `ai_decisions` feature, a hard cap of 50 results, and latest-first ordering. The only weak spot is the vague cross-reference 'same range rules as the report', which leaves the agent to infer the actual range constraints.

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?

One dense paragraph that front-loads the core purpose, then scope, then constraints, then gating requirements in bold. The opening sentence duplicates the title, but otherwise every clause carries information.

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 12-parameter, all-optional read tool with no output schema, the description covers the essentials an agent needs: relationship to the report, result cap, ordering, and permission/feature gates. The one gap is that it never sketches the shape of a returned conversation record, which the absent output schema leaves to the agent's guess.

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 83%, so the schema already documents nearly every filter including enum meanings. The description mostly restates the filter list (opening/closing sentiment, risk flag, frustration, handler, agent, inbox, team) and adds no syntax, default, or combination semantics beyond what the schema provides; 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 ('List conversations by sentiment') and immediately clarifies scope as 'The conversations behind a cell of the sentiment report', which distinguishes it from the report tool itself. An agent can tell this is the drill-down companion to get_sentiment_report 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?

The 'conversations behind a cell of the sentiment report' framing plus 'Same range rules as the report' gives a clear context for when to reach for this tool rather than the aggregate report. It stops short of naming get_sentiment_report explicitly or stating when not to use it, so it is clear context without exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources