warp-mcp

Attach numbers to campaign

msg_assign_numbers

Attach your owned phone numbers to a 10DLC campaign, completing the required setup before sending messages from those numbers.

Instructions

Attach telephone numbers you own to one of your 10DLC campaigns. This is STEP 3 of the 10DLC flow (msg_create_brand → msg_create_campaign → assign numbers) and is required before msg_send will accept a number as from. Returns per-TN assigned/failed lists (failure reasons: not_found, not_owned, lookup_error, write_error); the response is NOT wrapped in the standard envelope. Errors: INVALID_PAYLOAD (400), NOT_FOUND (404, campaign not owned), TNIQ_ERROR (502).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "phone_numbers": "<phone_numbers>"
    },
    "name": "msg_assign_numbers"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Campaign ID (messaging-backend UUID, as returned by msg_list_campaigns / msg_create_campaign)
`phone_numbers`	Yes	Telephone numbers to attach, NANP format, e.g. ["13039813633"]

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Jul 8, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Describes the response format as 'per-TN assigned/failed lists' with specific failure reasons, and notes that the response is NOT wrapped in the standard envelope. This adds significant context beyond the annotations, which only indicate non-readonly and non-idempotent. No contradiction with 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?

Three sentences with no wasted words. Front-loaded with action, then flow context, then response/error details. Every sentence earns its place.

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

Completeness5/5

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

Given the simple parameter set and the presence of annotations, the description fully covers purpose, usage context, prerequisites, response format, and error scenarios. No gaps identified.

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

Parameters4/5

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

Schema coverage is 100% with clear descriptions for both parameters. The description adds context by explaining the campaign ID source (msg_list_campaigns / msg_create_campaign) and the NANP format example, which enhances understanding beyond the schema alone.

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 name and description clearly state 'Attach telephone numbers you own to one of your 10DLC campaigns.' It uses a specific verb ('attach'), identifies the resource ('telephone numbers' and 'campaign'), and positions it as step 3 of the 10DLC flow, distinguishing it from siblings like msg_remove_numbers.

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

Usage Guidelines5/5

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

Explicitly states it is step 3 of the flow, lists prerequisites (msg_create_brand, msg_create_campaign), and notes that it is required before msg_send. Also enumerates possible error types (INVALID_PAYLOAD, NOT_FOUND, TNIQ_ERROR) with HTTP status codes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server