RingCentral · Telephony
RINGCENTRAL_SEND_SMS
Send an SMS through the connected RingCentral extension. Use only after explicit user approval. Returns { id, uri, messageStatus, creationTime, from, to }.
- Provider
- RingCentral
- Access
- Write
- Category
- Telephony
- Version
- v1
Input schema
{
"type": "object",
"properties": {
"from": {
"type": "string",
"description": "Sender phone number on the connected RingCentral account."
},
"to": {
"type": "string",
"description": "Recipient phone number."
},
"text": {
"type": "string",
"description": "SMS text body."
}
},
"required": [
"from",
"to",
"text"
],
"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_send_sms 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.
Write action — gate behind explicit user approval and write scope.
Frequently asked
- How do I let an AI agent ringcentral send sms?
- Connect RingCentral to CybrLink, then expose the `ringcentral_send_sms` 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. Send an SMS through the connected RingCentral extension. Use only after explicit user approval. Returns { id, uri, messageStatus, creationTime, from, to }.
- Does the AI model see my RingCentral credentials when using RINGCENTRAL_SEND_SMS?
- No. CybrLink stores the credential in a token vault and injects it on the server for each call, so the model can take this action in RingCentral without the OAuth token or API key ever entering its context.