vapi-mcp-server

vapi_import_phone_number

Import a phone number into Vapi by providing the number, provider, provider ID, and token.

Instructions

Import a phone number to Vapi

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": {
      "number": "<number>",
      "provider": "<provider>",
      "providerId": "<providerId>",
      "providerToken": "<providerToken>"
    },
    "name": "vapi_import_phone_number"
  }
}

Input Schema

Name	Required	Description	Default
`number`	Yes
`provider`	Yes
`providerId`	Yes
`providerToken`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 21, 2026

TDQS

C2.3/5.0

Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits but only states a generic action. It fails to mention side effects (e.g., does it overwrite?), required permissions, or whether the operation is reversible. The brevity offers no transparency beyond the bare action.

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

Conciseness2/5

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

The description is very short at one sentence, which is concise but at the expense of essential information. It under-specifies the tool's behavior and parameters, making it insufficient for practical use.

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

Completeness1/5

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

Given the complexity of four required parameters with no schema descriptions, no output schema, and no annotations, the description is woefully incomplete. It does not explain what the import entails, what the return value is, or any constraints, leaving the agent without enough information to invoke the tool correctly.

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

Parameters1/5

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

The input schema defines four required parameters (number, provider, providerId, providerToken) with no descriptions. The tool description adds no information about their meaning or expected format, which is critical given 0% schema description coverage.

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 tool's purpose as importing a phone number to Vapi, using a specific verb and resource. However, it does not distinguish from the sibling tool 'vapi_buy_phone_number', which also involves obtaining a phone number, leaving ambiguity about when to use each.

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, nor does it mention any prerequisites or context for importing a phone number. This leaves the agent without direction for selection.

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