Skip to main content
Glama
team-telnyx

Telnyx MCP Server

Official
by team-telnyx
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

create_messaging_profile

Set up a messaging profile to configure SMS/MMS sending rules, webhooks, number pools, and spending controls for Telnyx communications.

Instructions

Create a messaging profile.

Args:
    name: Required. A user friendly name for the messaging profile.
    whitelisted_destinations: Required. List of destinations to which messages are allowed to be sent (ISO 3166-1 alpha-2 country codes). Use ["*"] to allow all destinations.
    enabled: Optional boolean. Specifies whether the messaging profile is enabled. Defaults to True.
    webhook_url: Optional. The URL where webhooks related to this messaging profile will be sent.
    webhook_failover_url: Optional. The failover URL for webhooks if the primary URL fails.
    webhook_api_version: Optional. Webhook format version ("1", "2", or "2010-04-01"). Defaults to "2".
    number_pool_settings: Optional dictionary. Number pool configuration with possible settings:
        - use_pool: Boolean indicating whether to use number pool.
        - sticky_sender: Boolean indicating whether to use sticky sender.
        - pool_weights: Dictionary mapping phone number types to weights.
    url_shortener_settings: Optional dictionary. URL shortener configuration with possible settings:
        - enabled: Boolean indicating whether URL shortening is enabled.
        - domains: List of domains to be shortened.
    alpha_sender: Optional. The alphanumeric sender ID for destinations requiring it.
    daily_spend_limit: Optional. Maximum daily spend in USD before midnight UTC.
    daily_spend_limit_enabled: Optional boolean. Whether to enforce the daily spend limit.
    mms_fall_back_to_sms: Optional boolean. Enables SMS fallback for MMS messages.
    mms_transcoding: Optional boolean. Enables automated resizing of MMS media.

Returns:
    Dict[str, Any]: Response data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYes

Tool Definition Quality

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It implicitly indicates a write operation ('Create') and documents many configuration options, but doesn't explicitly state permission requirements, rate limits, error conditions, or what happens on success/failure. It provides moderate context about what gets created but lacks comprehensive behavioral details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections for Args and Returns, but it's overly verbose with detailed parameter documentation that might be better handled in the schema. While comprehensive, it could be more concise by focusing on high-level guidance rather than exhaustive parameter details that belong in structured fields.

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

Completeness4/5

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

Given the complexity of creating a messaging profile with many configuration options, no annotations, and no output schema, the description provides substantial context through detailed parameter documentation. However, it lacks information about the return value structure beyond 'Dict[str, Any]' and doesn't cover error handling or operational constraints, leaving some gaps in completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite having 0% schema description coverage (the schema only shows a generic 'request' object), the description provides extensive parameter documentation with 14 detailed parameters, including required/optional status, data types, defaults, and specific usage examples. This fully compensates for the poor schema coverage and adds substantial value beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Create' and the resource 'messaging profile', making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'update_messaging_profile' or explain what distinguishes creation from updating, which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'update_messaging_profile' or 'get_messaging_profile'. There's no mention of prerequisites, dependencies, or typical use cases, leaving the agent with insufficient context for proper tool selection.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/team-telnyx/telnyx-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server