Skip to main content
Glama

List inboxes

list_inboxes
Read-onlyIdempotent

List the inboxes (channels) of this account with their settings: channel type, greeting, working hours, CSAT survey, auto-assignment, timezone and the website widget's colour and appearance.

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

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional: return only these fields of each record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / fields / items / enum
      Previous value: -[
      -  "id",
      -  "name",
      -  "channel_type",
      -  "greeting_enabled",
      -  "greeting_message",
      -  "working_hours_enabled",
      -  "csat_survey_enabled",
      -  "enable_auto_assignment",
      -  "out_of_office_message",
      -  "working_hours",
      -  "timezone",
      -  "allow_messages_after_resolved",
      -  "lock_to_single_conversation",
      -  "business_name",
      -  "help_center",
      -  "widget_color",
      -  "appearance"
      -]New value: +[
      +  "id",
      +  "name",
      +  "channel_type",
      +  "greeting_enabled",
      +  "greeting_message",
      +  "working_hours_enabled",
      +  "csat_survey_enabled",
      +  "enable_auto_assignment",
      +  "out_of_office_message",
      +  "working_hours",
      +  "timezone",
      +  "allow_messages_after_resolved",
      +  "lock_to_single_conversation",
      +  "business_name",
      +  "help_center",
      +  "widget_color",
      +  "appearance",
      +  "allowed_domains",
      +  "csat_config"
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and side-effect profile are covered by structured data. The description adds useful content disclosure by naming the settings that come back (greeting, working hours, CSAT, widget colour/appearance), but says nothing about pagination, ordering, or required permissions.

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?

A single front-loaded sentence that begins with the verb and resource before the detail. The trailing enumeration of settings is a bit list-heavy but each item earns its place by telling the agent what the response contains in the absence of an output schema.

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?

Simple, single-parameter read tool with full schema coverage and rich annotations; the description closes the main remaining gap by describing returned content since no output schema exists. Missing only pagination/ordering behavior, which is minor at this complexity.

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?

Only one optional parameter and schema description coverage is 100%, so the enum of allowed field names already fully documents it. The description's field list (channel type, greeting, working hours, CSAT, auto-assignment, timezone, widget colour) mirrors a subset of that enum and adds mild orientation but no syntax or default guidance; 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?

Specific verb+resource: 'List the inboxes (channels) of this account' plus an enumeration of the returned settings. It implicitly separates itself from the singular get_inbox/update_inbox siblings through the plural 'list', but never names them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance and no named alternatives. The agent must infer from 'List the inboxes of this account' that this is the bulk-enumeration option versus get_inbox for a single inbox, and nothing tells it when this tool is not appropriate.

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