Blujay MCP Server

Official

by blujayhq

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

List conversations

list_conversations

Read-only

Lists conversations most recently active first and filters them by a person's phone number or email or by one of your phone numbers.

Instructions

Your conversations, most recently active first. Filter to one person with with (their phone number or email) or to one of your numbers with on_number.

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

Input Schema

Name	Required	Description
`with`	No	Only conversations with this person: phone number or email.
`limit`	No
`cursor`	No	next_cursor from a previous call, for the next page.
`on_number`	No	Only conversations on this phone number of yours.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Nov 11, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context beyond that: the result is scoped to the caller's own conversations and ordered by recency. It says nothing about pagination behavior or what a conversation record contains, which matters since there is no output schema.

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 short sentences with the result shape and ordering front-loaded, followed by the filtering options. Every clause carries information; nothing is padding.

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?

For a read-only list tool with no output schema, an agent would benefit from knowing what fields a conversation exposes and how paging terminates, neither of which is covered. The ordering and filter semantics it does provide are correct but leave those gaps.

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 coverage is 75%, so most parameters are documented structurally. The description reinforces the meaning of `with` and `on_number` and frames them as alternative filters, but adds no detail on `limit` (which has no schema description at all) or `cursor` beyond what the schema states. Baseline 3 is appropriate.

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 the resource and scope ('Your conversations') plus the sort order ('most recently active first'), which tells an agent exactly what a call yields. It does not differentiate itself from siblings such as get_conversation (single conversation) or find_unanswered (filtered subset), so it falls short of a 5.

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?

The description explains how to narrow the result to a person via `with` or to one of the user's numbers via `on_number`, which implies the intended usage. It never says when to prefer this over get_conversation or find_unanswered, so the guidance is implied rather than explicit.

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