Skip to main content
Glama

Customs for one campaign

set_campaign_customs

Override how one campaign sounds and who it is (admin only). Customs: tone, opening (said as the first line; {name} and {team} fill in), closing, say, never_say, customs, knock_line. Identity, for a campaign that calls as a different company: spoken_name, pronunciation, about, website, caller_name. Handoff: closer_name and handoff_number, the person and phone that ring when a live prospect wants a human on this campaign's calls (instead of the workspace's human line). Null returns a key to the team default.

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

Input Schema

NameRequiredDescriptionDefault
customsYes
campaign_idYesCampaign id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish this is a non-destructive, closed-world mutation, so the bar is lower. The description adds real value with the admin authorization requirement and the reset-to-default semantics of a null value. It omits the key behavioral question for a nested-object write: whether omitted keys are merged or replaced, and whether changes affect calls already in flight.

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?

Front-loads the one-line purpose and admin gate, then uses the body for the key catalogue that the schema cannot provide. The 'Customs:'/'Identity:'/'Handoff:' labeling keeps a long enumeration scannable, though the sentence is dense and repeats the word 'customs' inside its own key list.

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 tool with an untyped nested object and no output schema, the definition covers the key vocabulary, the admin prerequisite, and null/reset behavior — enough to attempt a call correctly. The gaps (merge-vs-replace semantics for the customs object, key value types) are real but narrow.

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 only 50% and the 'customs' parameter is an untyped open object, so the description carries almost the entire burden — and does so by enumerating three key families (tone/opening/closing/say/never_say/knock_line, identity keys, handoff keys) plus the {name}/{team} placeholder syntax in 'opening'. What remains missing is the value type or format of individual keys, so an agent still has to guess string vs boolean vs list for entries like 'never_say'.

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?

Opens with a concrete verb and scope: 'Override how one campaign sounds and who it is (admin only)' — an agent can tell this mutates per-campaign voice/identity settings. It distinguishes itself from the workspace-level default by referencing 'the team default' and 'the workspace's human line', though it never names the sibling tool that sets those defaults.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The '(admin only)' gate and the 'Null returns a key to the team default' line imply this is the per-campaign override layer sitting on top of workspace settings, which is useful routing context. However, it never states explicitly when to prefer this over the team-level equivalent, nor what to do if the caller is not an admin.

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.