Skip to main content
Glama

Save campaign setup · 保存活动准备设置(短.在线)

save_campaign_setup
Idempotent

保存可复用的列映射与输出格式;不复制链接身份。需要已注册账号。 Save reusable column mappings and output format; does not copy link identities. Registered account required.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "output_format": {
        "png_size": 512,
        "qr_format": "png"
      },
      "column_mappings": {
        "label_column": "title",
        "destination_column": "url"
      }
    },
    "name": "save_campaign_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
output_formatNoDefault QR output options for this setup.
column_mappingsNoSpreadsheet column mapping for reusable setups.
naming_conventionNoFilename or label pattern for QR files.
preferred_languageNoDefault locale for generated copy.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover write/idempotent/non-destructive/openWorld, so the description's job is to add beyond that. It does: the auth prerequisite and the explicit non-effect on link identities are behavioral facts not present in the annotations. It does not describe overwrite semantics (whether saving replaces an existing setup), which would have completed the picture.

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?

Two short, front-loaded clauses per language with the scope and prerequisite stated up front; no filler. The bilingual duplication doubles the token footprint, though that appears intentional rather than accidental verbosity.

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?

An output schema exists, so return values need no explanation, and the auth requirement is stated. What remains thin is the relationship to the apply/get siblings and whether repeated saves overwrite prior setups — minor against an otherwise well-covered definition.

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 description coverage is 100%, so the schema already documents all four parameters including the nested output_format and column_mappings objects. The description only gestures at two of the four fields and adds no format or constraint detail beyond the schema, so baseline 3 applies.

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 ('Save') and a concrete resource ('reusable column mappings and output format'), which an agent can map to the campaign-setup family. It does not name which sibling performs the complementary step (e.g. apply_campaign_setup), so differentiation is by scope statement rather than explicit routing.

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 a clear prerequisite ('Registered account required') and a negative scope ('does not copy link identities'), which tells the agent what this call will and will not accomplish. It stops short of naming an alternative tool for the apply/execute step, so the when-to-use-instead half of the guidance is missing.

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