RingCentral · Telephony

RINGCENTRAL_LIST_MESSAGES

List RingCentral message-store records for the connected extension. Returns { records, navigation }.

Provider
RingCentral
Access
Read
Category
Telephony
Version
v1

Input schema

{
  "type": "object",
  "properties": {
    "direction": {
      "type": "string",
      "enum": [
        "Inbound",
        "Outbound"
      ],
      "description": "Optional message direction filter."
    },
    "messageType": {
      "type": "string",
      "enum": [
        "Fax",
        "SMS",
        "VoiceMail",
        "Pager",
        "Text"
      ],
      "description": "Optional message type filter."
    },
    "perPage": {
      "type": "number",
      "description": "Max records to return (default 10)."
    },
    "page": {
      "type": "number",
      "description": "Page number to return (default 1)."
    }
  },
  "additionalProperties": false
}

How to call it

Expose this tool to any MCP-capable agent (Claude, GPT, or your own) through CybrLink's MCP server. The agent calls ringcentral_list_messages with arguments matching the schema above.

CybrLink validates the input, injects the connected RingCentral credentials server-side, and runs a single scoped provider API call through the shared proxy — the same guarded path as the generic call_api tool. The raw secret never reaches the model, and the response is trimmed to just the fields the agent needs.

Frequently asked

How do I let an AI agent ringcentral list messages?
Connect RingCentral to CybrLink, then expose the `ringcentral_list_messages` tool to any MCP-capable agent (Claude, GPT, or a custom framework). The agent calls it with typed arguments; CybrLink injects the RingCentral credential server-side and runs one scoped API call. List RingCentral message-store records for the connected extension. Returns { records, navigation }.
Does the AI model see my RingCentral credentials when using RINGCENTRAL_LIST_MESSAGES?
No. CybrLink stores the credential in a token vault and injects it on the server for each call, so the model can read this data from RingCentral without the OAuth token or API key ever entering its context.