Skip to main content
Glama
Ringer

warp-mcp

by Ringer

Update 10DLC brand

msg_update_brand
Idempotent

Replace an existing 10DLC brand with a complete updated brand object to correct identity details, which may initiate TCR re-verification.

Instructions

Full replace (PUT) of one of your 10DLC brands — supply the complete brand object, not just changed fields. Use to correct brand identity details, which may trigger TCR re-verification. Errors: INVALID_PAYLOAD (400), NOT_FOUND (404), TNIQ_ERROR (502).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesBrand ID (messaging-backend UUID, as returned by msg_list_brands / msg_create_brand)
einNoTax ID / EIN, e.g. "12-3456789" (US). Required for company registrations; improves trust score.
cityNoCity, e.g. "Denver"
emailNoBrand contact email address
phoneNoSupport/contact phone in E.164 format, e.g. "+13035551212"
stateNoState/region code, e.g. "CO"
streetNoStreet address, e.g. "123 Main St"
countryNoCountry as 2-letter ISO code, e.g. "US"
websiteNoBrand website URL, e.g. "https://acme.example.com"
verticalNoIndustry vertical code (see msg_list_verticals for the valid list), e.g. RETAIL
last_nameNoContact last name (required for SOLE_PROPRIETOR)
first_nameNoContact first name (required for SOLE_PROPRIETOR)
entity_typeNoBrand entity type (see msg_list_entity_types for the valid list), e.g. PRIVATE_PROFIT
postal_codeNoPostal/ZIP code, e.g. "80202"
company_nameNoLegal company name as registered, e.g. "Acme Coffee LLC". Required for non-SOLE_PROPRIETOR entity types.
display_nameNoBrand display/marketing name, e.g. "Acme Coffee"
mobile_phoneNoMobile phone in E.164 format (used for SOLE_PROPRIETOR OTP verification)
reference_idNoYour own free-form reference ID for this brand
stock_symbolNoStock ticker symbol (PUBLIC_PROFIT brands only)
stock_exchangeNoStock exchange, e.g. NASDAQ, NYSE (PUBLIC_PROFIT brands only)
alt_business_idNoAlternate business identifier, e.g. DUNS number
ein_issuing_countryNoEIN issuing country as 2-letter ISO code, e.g. "US"
alt_business_id_typeNoType of the alternate business ID, e.g. DUNS, LEI, GIIN
Behavior4/5

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

Annotations indicate idempotentHint=true and destructiveHint=false. The description goes beyond by clarifying it's a full replace (PUT), which explains idempotency, and warns about potential TCR re-verification. This adds behavioral context not present in annotations.

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

Conciseness5/5

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

The description is two sentences, no wasted words. It front-loads the crucial 'full replace (PUT)' concept, then adds side effect and error codes. Every sentence adds value.

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 23 parameters and no output schema, the description adequately explains the operation type, side effect, and common errors. It could mention return values or success indicators, but the schema richness and annotations compensate. Sufficient for agent usage.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all parameters. The description does not add further semantics for individual parameters, but it reinforces the overall requirement to supply the complete object. Baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states it's a full replace (PUT) operation for a 10DLC brand, distinguishes it from partial updates by requiring the complete object, and specifies the use case of correcting brand identity details. It also mentions potential re-verification, adding context.

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

Usage Guidelines3/5

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

The description says 'Use to correct brand identity details', which implies the intended use case. However, it does not explicitly state when not to use (e.g., for partial updates) or mention alternatives like msg_create_brand or msg_update_campaign. The usage guidance is implied but lacks explicit exclusions.

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/Ringer/warp-mcp'

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