AgentLine
Server Details
Give AI agents a phone number. Voice calls, SMS, and phone number management for MCP clients.
- Status
- Unhealthy
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- AgentLineHQ/agentline-mcp
- GitHub Stars
- 0
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
push_call_context1 field changed- added
Input schema / properties / tokenAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Push token (alt to X-Push-Token header / body).", + "title": "token", + "type": "string" +}
1 tool update
- Added
push_call_context
1 tool update
- Changed
set_webhook2 fields changed- changed
Input schema / properties / secret / descriptionPrevious value: -"Optional HMAC signing secret. Auto-generated if omitted. Used to verify the X-AgentLine-Signature header on delivered payloads."New value: +"Optional HMAC signing secret. Auto-generated if omitted. Used to verify the signature header on delivered payloads." - added
Input schema / properties / signature_headerAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Header name for the HMAC-SHA256 signature of the raw body. Defaults to 'X-Webhook-Signature' (natively verified by Hermes, OpenClaw, and other agent platforms). Set to 'X-Hub-Signature-256' for GitHub-style verification, or any custom header name your platform expects. Omit to keep the existing value when updating.", + "title": "signature_header", + "type": "string" +}
2 tool updates
- Changed
create_agent1 field changed- removed
Input schema / properties / voice_modeRemoved value: -{ - "default": "hosted", - "description": "Where the agent's 'brain' runs. 'hosted' = AgentLine's LLM (Deepgram STT → LLM → Cartesia TTS). 'webhook' = the agent's configured webhook receives each caller utterance and returns what the agent says (2-way), for both inbound and outbound. Requires a webhook URL to be configured.", - "enum": [ - "hosted", - "webhook" - ], - "title": "voice_mode", - "type": "string" -}
- Changed
update_agent1 field changed- removed
Input schema / properties / voice_modeRemoved value: -{ - "anyOf": [ - { - "enum": [ - "hosted", - "webhook" - ], - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Switch the agent's brain: 'hosted' (LLM) or 'webhook' (the agent's webhook becomes the 2-way conversational brain). Webhook mode requires a configured webhook URL.", - "title": "voice_mode", - "type": "string" -}
6 tool updates
- Changed
create_agent1 field changed- added
Input schema / properties / voice_modeAdded value: +{ + "default": "hosted", + "description": "Where the agent's 'brain' runs. 'hosted' = AgentLine's LLM (Deepgram STT → LLM → Cartesia TTS). 'webhook' = the agent's configured webhook receives each caller utterance and returns what the agent says (2-way), for both inbound and outbound. Requires a webhook URL to be configured.", + "enum": [ + "hosted", + "webhook" + ], + "title": "voice_mode", + "type": "string" +}
- Added
delete_webhook - Added
get_webhook - Added
set_webhook - Added
test_webhook - Changed
update_agent1 field changed- added
Input schema / properties / voice_modeAdded value: +{ + "anyOf": [ + { + "enum": [ + "hosted", + "webhook" + ], + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Switch the agent's brain: 'hosted' (LLM) or 'webhook' (the agent's webhook becomes the 2-way conversational brain). Webhook mode requires a configured webhook URL.", + "title": "voice_mode", + "type": "string" +}
2 tool updates
- Added
list_feedback - Added
submit_feedback
2 tool updates
- Changed
create_agent1 field changed- added
Input schema / properties / owner_phoneAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Owner's phone number in E.164 format (e.g. '+12125551234'). Calls from this number enter task mode — the agent treats speech as executable instructions.", + "title": "owner_phone", + "type": "string" +}
- Changed
update_agent1 field changed- added
Input schema / properties / owner_phoneAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Updated owner phone number in E.164 format for task mode", + "title": "owner_phone", + "type": "string" +}
3 tool updates
- Changed
create_agent1 field changed- removed
Input schema / properties / model_tierRemoved value: -{ - "default": "balanced", - "description": "LLM model tier: 'turbo' (fastest, GPT-4o-mini), 'balanced' (default), or 'max' (highest quality, GPT-4o)", - "enum": [ - "turbo", - "balanced", - "max" - ], - "title": "model_tier", - "type": "string" -}
- Changed
make_outbound_call1 field changed- removed
Input schema / properties / model_tierRemoved value: -{ - "default": "balanced", - "description": "LLM model tier for this call: 'turbo', 'balanced', or 'max'", - "enum": [ - "turbo", - "balanced", - "max" - ], - "title": "model_tier", - "type": "string" -}
- Changed
update_agent1 field changed- removed
Input schema / properties / model_tierRemoved value: -{ - "anyOf": [ - { - "enum": [ - "turbo", - "balanced", - "max" - ], - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Updated LLM model tier: 'turbo', 'balanced', or 'max'", - "title": "model_tier", - "type": "string" -}
3 tool updates
- Changed
create_agent2 fields changed- changed
Input schema / properties / initial_greeting / descriptionPrevious value: -"What the AI agent says when a call connects (e.g. 'Hello, how can I help you today?')"New value: +"Default opening line spoken on ALL calls (inbound and outbound), e.g. 'Hello, how can I help you today?'. Can be overridden per-call via POST /v1/calls." - changed
Input schema / properties / system_prompt / descriptionPrevious value: -"Instructions that define the agent's personality and behavior during phone calls"New value: +"Default instructions for the agent's personality and behavior on ALL calls (inbound and outbound). Can be overridden per-call via POST /v1/calls."
- Changed
make_outbound_call2 fields changed- changed
Input schema / properties / initial_greeting / descriptionPrevious value: -"Override the agent's greeting for this call only"New value: +"Per-call greeting override. Replaces the agent's default greeting for this call ONLY. If omitted, the agent's default initial_greeting is used." - changed
Input schema / properties / system_prompt / descriptionPrevious value: -"Override the agent's default system prompt for this call only"New value: +"Per-call system prompt override. Replaces the agent's default prompt for this call ONLY. If omitted, the agent's default system_prompt is used."
- Changed
update_agent2 fields changed- changed
Input schema / properties / initial_greeting / descriptionPrevious value: -"Updated greeting message spoken when calls connect"New value: +"Updated default greeting for ALL future calls (inbound and outbound)" - changed
Input schema / properties / system_prompt / descriptionPrevious value: -"Updated instructions for the agent's phone call behavior"New value: +"Updated default instructions for ALL future calls (does not affect calls already in progress)"
21 tool updates
- First observed
buy_phone_number - First observed
create_agent - First observed
delete_agent - First observed
get_account_balance - First observed
get_account_voice - First observed
get_agent - First observed
get_call_details - First observed
get_call_transcript - First observed
get_expenditure_breakdown - First observed
hangup_call - First observed
list_agents - First observed
list_available_voices - First observed
list_calls - First observed
list_messages - First observed
list_phone_numbers - First observed
make_outbound_call - First observed
peek_events - First observed
poll_events - First observed
reset_account_voice - First observed
set_account_voice - First observed
update_agent
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Give AI agents real phone numbers, messages, and voice calls via MCP.
Phone, SMS & email for AI agents — one remote MCP endpoint, OAuth login, zero install.
Virtual phone numbers for AI agents — rent numbers in 200+ countries, receive SMS.
Give AI agents a phone layer for consent-based calls, transcripts, summaries, and outcomes.
1
Related MCP Servers
- AlicenseAqualityDmaintenanceGives AI agents phone numbers, email, SMS, and voice calls as MCP tools, enabling them to provision numbers, capture 2FA codes, send messages, and make calls.15MIT

Dial MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to provision phone numbers, send SMS, place AI voice calls, and react to inbound events via the Dial communication stack, all through MCP tools.95MIT- AlicenseNot gradedqualityDmaintenanceMCP server for provisioning dedicated real-SIM US phone numbers, receiving inbound SMS, and extracting OTP codes. Built for AI agents automating phone verification workflows.471MIT
- AlicenseAqualityDmaintenanceGives AI agents real phone numbers to receive SMS and extract verification codes through tool calls.643MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
Each tool targets a distinct resource and action (e.g., get_agent vs list_agents, get_call_details vs get_call_transcript, peek_events vs poll_events). There is no ambiguity or overlap between tool purposes.
All tool names follow a consistent verb_noun pattern (e.g., create_agent, list_calls, buy_phone_number, set_webhook). No mixing of conventions or unclear naming.
27 tools cover a broad telephony AI platform. While slightly above the typical 3-15 range, each tool serves a distinct purpose and the count is justified by the feature set (agents, calls, SMS, webhooks, events, account, feedback).
Core lifecycle for agents, calls, and webhooks is covered. However, SMS sending is missing (only list_messages exists) and there is no tool to release a phone number, leaving notable gaps in the domain.