Skip to main content
Glama

Import contacts

import_campaign_contacts

Add contacts to a campaign from CSV text (header row: company, phone, name, title, email).

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>",
      "csv": "<csv>"
    },
    "name": "import_campaign_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCampaign id.
csvYesCSV text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the concrete CSV header contract, but omits important import behavior: whether rows append or replace, how duplicates are handled, and whether partial/invalid rows abort the whole import. Those gaps keep it at a 3.

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?

A single front-loaded sentence carrying the action and the format contract with no filler. Nothing in it could be removed without losing information.

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?

For a two-parameter import tool the input contract is adequately covered, but with no output schema the description should say what a successful import reports (counts, per-row errors) and how failures behave. The duplicate and error semantics remain undefined.

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%, so the baseline is 3, but the description goes beyond the schema's terse 'CSV text.' by naming the exact header row and column order (company, phone, name, title, email). That is genuinely new meaning an agent needs to build a valid payload.

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 gives a specific verb+resource ('add contacts to a campaign') plus the transport format ('from CSV text'), which separates it from create_campaign and work_campaign. It stops short of explicitly naming a sibling or scope boundary, but the action is unambiguous.

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?

Usage is only implied by the phrasing 'add contacts to a campaign' – there is no statement of when to prefer this over create_campaign or work_campaign, nor any prerequisite (e.g. campaign must exist, contacts must be new). An agent can infer the intent but gets no routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.