Skip to main content
Glama
MakingChatbots

Genesys Cloud MCP Server

by MakingChatbots
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

search_queues

Search routing queues by name with wildcard support. Returns matching queues with ID, description, member count, and pagination details for easy navigation.

Instructions

Searches for routing queues based on their name, allowing for wildcard searches. Returns a paginated list of matching queues, including their Name, ID, Description (if available), and Member Count (if available). Also provides pagination details like current page, page size, total results found, and total pages available. Useful for finding specific queue IDs, checking queue configurations, or listing available queues.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name (or partial name) of the routing queue(s) to search for. Wildcards ('*') are supported for pattern matching (e.g., 'Support*', '*Emergency', '*Sales*'). Use '*' alone to retrieve all queues
pageNumberNoThe page number of the results to retrieve, starting from 1. Defaults to 1 if not specified. Used with 'pageSize' for navigating large result sets
pageSizeNoThe maximum number of queues to return per page. Defaults to 100 if not specified. Used with 'pageNumber' for pagination. The maximum value is 500

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.4
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / pageNumber / maximum
      Added value: +9007199254740991
  2. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations provide only a title, so the description carries the behavioral transparency burden. It discloses return fields, pagination details, and the wildcard search behavior. For a read-only search tool this is solid, though it doesn't mention edge cases like empty results or error conditions.

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?

Three sentences with no waste. The description front-loads the core purpose, then gives return content and use cases. Each sentence contributes meaningful information.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple search tool with three scalar parameters and no output schema, the description adequately covers the operation, returned data, pagination behavior, and realistic use cases. Nothing essential is missing.

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%, including wildcard syntax, defaults, and maximum values for pageSize and pageNumber. The description adds minimal new parameter-level meaning beyond the schema—mainly reaffirming wildcard support—so the baseline score of 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?

The description opens with a specific verb and resource: 'Searches for routing queues based on their name.' It clearly distinguishes this tool from siblings like search_voice_conversations by focusing on routing queue metadata, and it explicitly states useful applications, so an agent can readily identify what this tool does.

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 description provides clear use cases: 'finding specific queue IDs, checking queue configurations, or listing available queues.' However, it does not explicitly name alternative tools or give when-not-to-use conditions, leaving some inference to the agent.

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

Install Server

Other Tools