argo-mcp

Update campaign

update_campaign

Idempotent

Update a campaign's display name and/or description. Both fields optional — only supplied fields are changed; pass an empty string to clear the description. GMs and co-GMs can call this; rule-system swaps remain WebApp-only.

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

Input Schema

Name	Required	Description
`campaignId`	Yes	ID of the campaign to update.
`campaignName`	No	New display name. Omit to leave unchanged.
`campaignDescription`	No	New description (setting, tone, premise). Omit to leave unchanged. Pass an empty string to clear the existing description.

Output Schema

Name	Required	Description	Default
`id`	Yes
`ruleSystem`	No
`campaignName`	Yes
`gameMasterId`	Yes
`gameSystemSlug`	No
`coGameMasterIds`	No
`campaignDescription`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 14, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description goes well beyond the annotations by explaining partial-update semantics (only supplied fields changed), how to clear the description with an empty string, and permission limitations. It adds valuable behavioral context without contradicting the idempotentHint and destructiveHint annotations.

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?

The description is two sentences, front-loaded with the purpose, and every clause earns its place. It balances scope, permissions, and update behavior without any fluff.

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?

The description covers purpose, permissions, update semantics, and important limitations. Since an output schema exists, return values need not be described. Minor gaps like error cases are acceptable and don't affect completeness significantly.

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

Parameters3/5

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

Schema coverage is 100% and each parameter is already well described. The description adds a general 'both fields optional' note but largely repeats what the schema already states, offering limited additional semantic value.

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?

The description clearly states the tool updates a campaign's display name and/or description, using a specific verb and resource. It distinguishes itself from the many sibling update_* tools by specifying the exact fields affected.

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?

It states who can use the tool (GMs and co-GMs) and explicitly excludes rule-system swaps (WebApp-only), giving clear context for when to use it. It does not explicitly name alternative tools, but the context is unambiguous.

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

All argo-mcp 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.