Skip to main content
Glama
team-telnyx

Telnyx MCP Server

Official
by team-telnyx
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

update_messaging_profile

Modify messaging profile settings in Telnyx to configure webhooks, enable features, set spending limits, and manage message delivery options.

Instructions

Update a messaging profile.

Args:
    profile_id: Required. The ID of the messaging profile to update.
    name: Optional. A user friendly name for the messaging profile.
    enabled: Optional boolean. Specifies whether the messaging profile is enabled.
    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").
    whitelisted_destinations: Optional list. Destinations to which messages are allowed (ISO 3166-1 alpha-2 country codes). Use ["*"] to allow all destinations.
    v1_secret: Optional. Secret used to authenticate with v1 endpoints.
    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
profile_idYes
requestYes

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a mutation operation ('update') but does not specify required permissions, whether changes are reversible, rate limits, or error handling. The mention of 'Returns: Dict[str, Any]: Response data' is vague and adds minimal value beyond indicating a dictionary output.

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 front-loaded with the core purpose but becomes lengthy due to exhaustive parameter documentation. While each parameter detail is useful, the structure could be more streamlined, and some redundancy exists (e.g., repeating 'Optional' for each param). It balances completeness with verbosity.

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

Completeness3/5

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

Given the tool's complexity (2 required params, 16 optional params, nested objects, no output schema, and no annotations), the description is partially complete. It excels in parameter semantics but lacks behavioral context, usage guidelines, and output details, making it adequate but with clear gaps for a mutation tool.

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?

The description compensates fully for the 0% schema description coverage by detailing all 16 optional parameters with clear semantics, including data types, constraints (e.g., ISO codes, boolean flags), and nested structures. This adds significant value beyond the minimal input schema, which only lists 'profile_id' and 'request' without specifics.

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 'update' and resource 'messaging profile', making the purpose evident. However, it does not differentiate from sibling tools like 'update_assistant' or 'update_connection', which have similar naming patterns but operate on different resources, so it lacks explicit sibling differentiation.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not mention prerequisites like needing an existing profile or compare with 'create_messaging_profile' or 'get_messaging_profile', leaving the agent without context for 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