Skip to main content
Glama

Update campaign targeting

update_campaign_targeting
DestructiveIdempotent

Change who a campaign finds. Pass only the fields to change; null clears a field. Industries are checked against LinkedIn's industry list exactly as the dashboard does, and names ZenMode cannot search for are reported instead of being dropped silently. Only targeting can be changed here. Nothing happens on LinkedIn at the moment you call this. ZenMode's campaign engine works through each campaign later, inside your daily and weekly limits, business hours and pacing. If the account is restricted, paused for the week, cooling down or switched off, the call is refused with the reason and when it lifts, and nothing changes. If the account has only used today's allowance, the change is accepted and the response says it will be worked through once the limit resets. Calls that only stop outreach (remove, pause, exclude, not interested) are never refused. An idempotency_key makes a retried call a no-op.

Input Schema

NameRequiredDescriptionDefault
companiesNoOnly keep people at these companies.
locationsNoLocations, e.g. "London, United Kingdom".
industriesNoLinkedIn industry names.
job_titlesNoJob titles, comma-separated or as a list.
search_urlNoA LinkedIn people search URL (https://www.linkedin.com/search/results/people/?...).
campaign_idYesThe campaign id, from list_campaigns.
idempotency_keyNoOptional. A unique string you make up for this exact change (8 to 128 letters, digits, - _ . :). If the call is repeated with the same key and the same arguments within 24 hours, nothing happens twice and the first result is returned again. Use a fresh key for every new change.
sales_navigator_search_urlNoA Sales Navigator search URL (needs Sales Navigator).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Far exceeds what the annotations convey: annotations only flag destructive/idempotent/not-readOnly, while the description discloses the async execution model (nothing happens on LinkedIn at call time), the refusal reasons and reset timing, and the interaction with daily/weekly limits, business hours, and pacing. It also explains idempotency_key retry semantics in behavioral terms.

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?

The one-line purpose is front-loaded and the rules that follow are dense but each sentence carries distinct behavioral information (clearing, validation, async timing, refusals, idempotency). It is longer than typical, but the length is justified by the tool's async and gated behavior.

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?

For an 8-parameter mutation tool with no output schema and non-trivial gating logic, the description covers what is needed to call it correctly: partial update semantics, validation behavior, refusal conditions, and the fact that the response reports deferred work. Nothing essential is missing.

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?

With 100% schema coverage the baseline is 3, but the description adds real meaning beyond the schema: 'Pass only the fields to change; null clears a field' defines partial-update and clear semantics, and it explains that industries are validated exactly against LinkedIn's list with unsearchable names reported rather than dropped.

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?

Opens with a concrete verb+resource and scope: 'Change who a campaign finds,' then narrows it ('Only targeting can be changed here'), which cleanly separates it from siblings like set_campaign_messages, pause_campaign, and get_campaign_targeting. An agent can identify the operation without opening the 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?

Gives strong conditional guidance on when the call is accepted vs refused (account restricted, paused, cooling down, switched off) and clarifies that stop-outreach calls are never refused. It does not, however, point to alternatives such as get_campaign_targeting for reading current targeting, so it stops short of full 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.