Skip to main content
Glama

Add Campaign Accounts

add_campaign_accounts
Idempotent

[Act · writes] Add one or more target companies to a Constellation campaign. Each account is a company you want to reach; map_constellation is then run per-account. Accounts already in the campaign (same linkedin_company_id, or same case-insensitive trimmed company_name) and repeats within the same call are not re-added; they are returned under skipped. Free — costs 0 credits.

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": {
      "campaign_id": "<campaign_id>",
      "accounts": "<accounts>"
    },
    "name": "add_campaign_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountsYesArray of companies to add (1-500 per call)
campaign_idYesTarget campaign id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare write/idempotent/non-destructive, and the description adds real value on top: the exact dedup keys (linkedin_company_id, or case-insensitive trimmed company_name), that intra-call repeats are also dropped, where skipped items surface, and that the call is free (0 credits). That is behavioral detail an agent could not get from the structured fields.

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

Conciseness4/5

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

Three sentences, front-loaded with a category tag and the core action; dedup and cost follow in the order an agent would need them. The dedup sentence is dense but every clause carries distinct information, so nothing is wasted.

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?

For a two-parameter write tool with no output schema, the definition covers cost, dedup outcome, and where skipped entries appear. It stops short of describing the success payload (e.g. what added accounts are returned as), which is the main residual gap.

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, and the description goes further by explaining that company_name matching is case-insensitive and trimmed and that linkedin_company_id is the primary identity key. It does not explain tier or employee_count, but those are self-evident from the 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?

Names a specific verb (Add) and resource (target companies/accounts) scoped to a Constellation campaign, and clarifies the downstream relationship to map_constellation. An agent can tell this apart from collection/segment adders in the sibling list without opening another schema.

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?

Establishes the workflow position clearly: accounts are added first, then map_constellation is run per-account. It does not explicitly rule out siblings like add_to_collection or add_to_segment, but the campaign-scoping language makes the intended context unambiguous.

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.

Resources