--deprecated

This connector has been deprecated

Replaced by io.github.no-fait/infinite-audience

Update Campaign

update_campaign

DestructiveIdempotent

Update a campaign name, description, or status. Set status=archived to soft-archive it while preserving linked audiences; set status=active to restore an archived campaign. Requires 'creator' scope.

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

Input Schema

Name	Required	Description
`name`	No	New display name for the campaign
`status`	No	New status for the campaign
`campaign_id`	Yes	The campaign ID to update
`description`	No	Campaign brief, goals, intended market, and desired outcomes; use an empty string to clear it

Output Schema

Name	Required	Description
`id`	Yes
`name`	Yes
`status`	Yes
`guidance`	No	Interpretation or recovery guidance for this result
`audiences`	Yes
`count_unit`	No
`page_count`	No	Number of objects on this page, not the organization total
`count_state`	No	Unknown means no count; available does not guarantee freshness. Recount for a current value.
`next_actions`	No	Suggested next calls using returned IDs and available scopes. Not executed and not user consent.
`population_input`	No	Population input used for the preview; IDs refer to their current saved definitions

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026
RemovedSep 27, 2026
AddedSep 26, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds real value beyond that by clarifying the 'destructive' action is a soft-archive that preserves linked audiences, and by naming the required 'creator' scope. It does not say whether partial updates are allowed or what happens when updating an already-archived campaign.

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 short sentences, zero filler, with the core action front-loaded and the status semantics and auth requirement following. Every sentence carries information the agent needs.

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?

With an output schema present and full parameter coverage, the description needn't explain return values, and it covers the risky status transition and the scope requirement. It stops short of describing partial-update behavior or error conditions for invalid state transitions, which would complete the picture for a destructive mutation.

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; the description earns an extra point by giving behavioral meaning to the status enum values (archived preserves linked audiences, active restores), which the schema only lists as bare values. name, description, and campaign_id add nothing beyond the schema, which is acceptable at full 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?

States a specific verb and resource ('Update a campaign') plus the exact mutable fields (name, description, status), so an agent knows precisely what it touches. It does not explicitly differentiate itself from siblings like create_campaign or get_campaign, but the verb makes the distinction self-evident.

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 concrete conditional guidance for the status field: archived = soft-archive, active = restore an archived campaign. It also states the 'creator' scope prerequisite. It lacks explicit when-not guidance or named alternatives (e.g., link_audience_to_campaign for association changes), which keeps it from a 5.

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

All --deprecated tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?