Skip to main content
Glama

Promo settings

get_promo_settings
Read-onlyIdempotent

How the artist's Promo settings stand: "Post these without waiting for your approval" (whether the weekly post about their music that Promo proposes, with Audora's Instagram invited as a collaborator, goes out on Instagram and Facebook without their press; TikTok always waits for it), "Keep it going each month" on each campaign between releases (whether its next month is planned on its last day, and what that costs), and "Your week" on each one (which weekdays post, what each is about, on which accounts; none set spreads the posts evenly). Change them with set_promo_settings.

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": "get_promo_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's job is domain semantics and it delivers: it explains what each setting actually governs, including the notable rule that TikTok always waits for approval regardless of the setting and that 'none set' spreads posts evenly. It does not describe the return payload's field names or any defaults for missing settings.

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?

All content is relevant, but it is delivered as one long sentence with deeply nested parentheticals that are hard to parse on a first read. The read/write routing ('Change them with set_promo_settings') is buried at the end instead of being front-loaded.

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 no output schema, the description carries the burden of conveying what comes back, and it does so at a conceptual level by explaining each setting's meaning. Field-level return shape is left unspecified, but for a single-parameter read-only getter this is close to sufficient.

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% and the single optional 'artist' parameter is fully documented there, including the label-vs-own-connection rule. The description adds no additional meaning about that parameter, 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?

The description makes clear this is a read of the artist's Promo settings and enumerates the three setting groups it covers (auto-publish approval, monthly campaign continuation, and weekday plan). The verb is implied by 'How ... stand' rather than stated, but the resource and scope are unambiguous and it names set_promo_settings as the mutation counterpart.

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 explicitly routes the agent to set_promo_settings for changes, which is the key when-to-use-vs-alternative signal for a getter. It does not state when reading is appropriate (e.g., before configuring a campaign), but the read/write split with the sibling is clear.

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