Skip to main content
Glama
Ringer

warp-mcp

by Ringer

Create 10DLC brand

msg_create_brand

Register a new 10DLC brand with TCR to start the 10DLC messaging compliance process. Provide entity type, contact info, and business details for TCR approval.

Instructions

Register a new 10DLC brand with TCR (The Campaign Registry) for your account. This is STEP 1 of the 10DLC flow: create brand → msg_create_campaign → msg_assign_numbers. Check msg_list_entity_types and msg_list_verticals for valid enum values first. Registration may incur TCR fees. Errors: INVALID_PAYLOAD/TNIQ_VALIDATION (400), TNIQ_ERROR (502, upstream TCR failure).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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?

Discloses registration may incur TCR fees and lists possible error codes (INVALID_PAYLOAD/TNIQ_VALIDATION 400, TNIQ_ERROR 502). Annotations indicate non-read-only and non-destructive. Missing success response behavior.

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?

Four sentences, each with a distinct purpose: core operation, flow placement, prerequisites, and error/fee info. No wasted words.

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?

Covers purpose, flow, prerequisites, and errors. Lacks success return value/response description, but given no output schema, it is reasonably complete for a registration tool with 22 parameters.

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 has 100% coverage with detailed parameter descriptions. Description adds context about EIN requirement for company registrations and SOLE_PROPRIETOR requirements, but does not significantly enhance parameter meaning beyond schema.

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?

Description clearly states the tool registers a new 10DLC brand with TCR, identifies it as step 1 of the flow, and distinguishes from sibling tools like msg_create_campaign and msg_delete_brand.

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

Usage Guidelines4/5

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

Explicitly states the tool is step 1 of the 10DLC flow and advises checking msg_list_entity_types and msg_list_verticals for valid enum values. Does not mention alternatives like when to use msg_update_brand instead.

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