Skip to main content
Glama

Change Promo settings

set_promo_settings
Destructive

Change the artist's Promo settings, as Settings › Connected and a campaign's menu in Promo do. Send only what changes. audora_approves_features: "Post these without waiting for your approval" on or off. keep_going: "Keep it going each month" on or off for one campaign between releases (get_promo_settings lists them, with what it costs). On, its next month is planned on its last day and charged its plan price then, each month; turning it on needs the artist's spend permission, turning it off never does. week: "Your week" for one campaign between releases (not 2 a day): weekday_shape names each weekday that posts (mon to sun) with one { kind, lanes }: kind "song" (A song of yours, still on repeat or out now.), "meet" (Who you are and how you make your music.), "with_audora" (Your own post with Audora invited on Instagram.); lanes are accounts the campaign posts to (get_promo_settings lists them), and with_audora keeps Instagram. At least as many days as its posts a week. Saving moves the posts not approved yet onto the new days; approved ones stay. null clears it. Confirm with the artist before you change any of these.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_promo_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekNo"Your week" for one campaign between releases.
artistNoOnly when you are connected as a label: the roster artist this call is for — their artist_user_id from list_roster, or their exact artist name. Required for every artist tool on a label connection. Leave it out on an artist's own connection.
keep_goingNo"Keep it going each month" for one campaign between releases.
audora_approves_featuresNo"Post these without waiting for your approval": true or false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: saving week moves not-yet-approved posts onto the new days while approved ones stay, null clears the setting, and enabling keep_going schedules and charges the plan price on each campaign's last day. These money and data-movement consequences are exactly the context an agent needs before a destructive write, and they are consistent with destructiveHint=true and idempotentHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the partial-update rule are front-loaded, and most content is load-bearing, but the body is a single dense block stitched together with semicolons and quoted UI labels, which makes the three settings harder to parse than they need to be. Structuring it per setting would preserve the information at lower reading cost.

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 4-parameter destructive write with nested objects and no output schema, the description covers each setting's meaning, side effects, clearing behavior, and permission gate. What is missing is modest: response shape (not required without an output schema) and any mention of failure/partial-apply behavior when several settings are sent together.

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 already 100%, so the baseline is 3; the description earns above that by defining the kind values in prose ("song", "meet", "with_audora"), explaining that lanes are posting accounts and that with_audora keeps Instagram, and stating the constraint that the week needs at least as many days as its posts a week. The only gap is that artist/label scoping is left entirely to the schema.

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?

States a specific verb and resource ("Change the artist's Promo settings") and locates it in the product UI ("Settings › Connected and a campaign's menu in Promo"). It also names the read counterpart (get_promo_settings) that lists campaigns and costs, so an agent can tell it apart from the sibling immediately.

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 direct operating guidance: "Send only what changes" (partial update), "get_promo_settings lists them, with what it costs" for discovering valid campaign IDs, and "Confirm with the artist before you change any of these." It also states a precondition that gates usage — turning keep_going on requires the artist's spend permission while turning it off does not. It stops short of an explicit 'do not use this to read settings' routing statement, but the direction is unambiguous.

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