agentline-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTLINE_API_KEY | Yes | API key for Agentline, starts with ag_live_ or ag_test_ | |
| AGENTLINE_BASE_URL | No | Override for self-hosted / staging | https://api.agentline.dev |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| provision_numberA | Provision a phone number the agent can use — for receiving SMS (e.g. 2FA), sending SMS, or placing/receiving voice calls. Use this BEFORE signing up for a service that asks for a phone number, or
before making outbound calls. If Returns a dict with |
| release_numberA | Release a previously provisioned phone number. Call this when done to
avoid ongoing Telnyx monthly charges. Pass the E.164 |
| list_numbersA | List all phone numbers currently provisioned on this account. Useful when the agent needs to find a number it forgot about, or audit what's active. |
| send_smsA | Send an outbound SMS from a provisioned number. |
| wait_for_smsA | Long-poll (blocking up to
Returns the message dict (with |
| capture_codeA | All-in-one 2FA capture: provision a fresh phone number, wait for an incoming SMS verification code (4-8 digits by default), then release the number. THE killer flow for signups. Typical use: call this, take Set |
| make_callA | Place an outbound AI voice call. An AI agent answers when the recipient
picks up and follows Returns immediately with the
|
| get_callA | Get status, transcript, and summary for a call. Call this after
|
| hangup_callA | End an in-progress call immediately. No-op / error if the call already terminated. |
| create_email_addressA | Provision a new email address for sending and receiving mail. Use this when signing up for services that require email verification — the agent gets a real inbox.
|
| list_email_addressesA | List all email addresses currently provisioned on this account. |
| release_email_addressA | Release a provisioned email address. Pass the |
| send_emailB | Send an outbound email from a provisioned address. |
| wait_for_emailA | Long-poll (blocking up to
|
| capture_email_codeA | All-in-one email verification capture: provision an email address, wait for an incoming verification code (4-8 digits by default), release the address. Use for services that email verification codes instead of SMS. Returns |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Each tool has a clearly distinct purpose. Even related tools like capture_code and wait_for_sms are differentiated by their level of abstraction (all-in-one vs. low-level blocking wait) and descriptions make the boundaries clear.
All tool names use snake_case and follow a consistent verb_noun pattern (e.g., capture_code, create_email_address, send_sms). Minor deviations like provision_number instead of create_number are still interpretable and follow the same style.
15 tools is well-scoped for the communication/verification domain. The set covers provisioning, sending, receiving, and releasing for both phone numbers and email, plus call handling, without being bloated.
Core CRUD-like operations are present for phone numbers and email (create/list/release, send/wait). The call lifecycle is covered (make, get, hangup). Missing are update operations for resources and call recording retrieval, but these are minor gaps for the primary use case.