Skip to main content
Glama

Update account settings

update_account_settings
DestructiveIdempotent

Changes an account's persona (up to 4,000 characters), schedule_times (comma-separated HH:MM in the account time zone, up to 8), review_before_publish, auto_reply_enabled, auto_thread, auto_link_to_comment, enabled, random posting (random_schedule, random_per_day, random_window, and random_exclude: up to 3 ranges such as 17:00-18:00 that random times skip), and content_rules (max_chars, min_chars, forbid_cta, forbid_hashtags, banned_phrases, facts as the only numbers the AI may use, forbid_causal_claims, judge_claims, one_fact_per_post, mention_limits, enforce warn or block). Only the fields sent are changed, except content_rules, which is replaced as a whole. if_match (the guardrails etag) makes a concurrent change answer 412 instead of overwriting; reason (up to 200 characters) is stored in the revision; dry_run:true previews whether the change would apply, ask the owner or be denied, without writing anything. A change that loosens a guardrail may wait for the owner's confirmation. Applies when the user asks to change voice, posting times, review mode, auto-reply or content rules.

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": {
      "account_id": "<account_id>"
    },
    "name": "update_account_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoWhy, up to 200 chars (optional, 1.9.0)
dry_runNotrue = preview only (1.9.0); at most 10 a minute per key
enabledNoMaster switch
personaNoBrand persona, up to 4000 chars
if_matchNoguardrails.etag from get_account_settings (optional, 1.9.0)
account_idYesAccount id
auto_threadNoAuto-split >500 chars
content_rulesNoStructured rules: max_chars, min_chars, forbid_cta, forbid_hashtags, banned_phrases[], facts[] (allowed numbers as plain sentences), forbid_causal_claims, judge_claims (model reviews for unsupported conclusions), one_fact_per_post, mention_limits [{phrase,max}], enforce (warn|block). null clears.
random_windowNoHH:MM-HH:MM, start before end; 00:00-23:59 = whole day
random_excludeNoUp to 3 HH:MM-HH:MM ranges random times skip, no midnight crossing, no overlap; [] clears
random_per_dayNoRandom posts per day, 1-30
schedule_timesNoComma-separated HH:MM, up to 8
random_scheduleNoRandom times every day instead of schedule_times (1.21.0)
auto_reply_enabledNoAI replies to comments on own posts
auto_link_to_commentNoLinks go to first comment
review_before_publishNoAI drafts wait for approval

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / random_exclude
      Added value: +{
      +  "description": "Up to 3 HH:MM-HH:MM ranges random times skip, no midnight crossing, no overlap; [] clears",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / random_per_day
      Added value: +{
      +  "description": "Random posts per day, 1-30",
      +  "type": "integer"
      +}
    • addedInput schema / properties / random_schedule
      Added value: +{
      +  "description": "Random times every day instead of schedule_times (1.21.0)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / random_window
      Added value: +{
      +  "description": "HH:MM-HH:MM, start before end; 00:00-23:59 = whole day",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well past the annotations: it discloses partial-update semantics ('Only the fields sent are changed, except content_rules, which is replaced as a whole'), optimistic concurrency via if_match returning 412, audit via reason, dry_run's non-writing preview, and that guardrail-loosening changes may require owner confirmation. These are exactly the mutation side-effects an agent needs and are not in the schema or annotations.

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?

The lead sentence is a single run-on that dumps all 16 settings inline, largely duplicating field descriptions already present at 100% schema coverage. The valuable behavioral notes (if_match, dry_run, content_rules replacement, guardrail confirmation) are buried mid-paragraph rather than 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?

For a destructive, non-read-only mutation with no output schema, the description covers write semantics, concurrency conflicts, preview behavior, and deferred-approval outcomes well. It omits what a successful response looks like (e.g., revision id) and the effect of enabled=false on existing schedules, but nothing critical to correct invocation is missing.

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 baseline is 3; the description adds real cross-field meaning, clarifying that content_rules is replaced wholesale, that facts are the only numbers the AI may use, and that if_match is the guardrails etag. Some field descriptions (enabled, auto_thread) are merely restated from the schema rather than expanded.

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 specific verb and resource ('Changes an account's persona, schedule_times, ...') and enumerates the exact mutable fields, so the agent knows precisely what is modified. It does not, however, differentiate itself from close siblings like apply_account_settings or preview_account_settings, which an agent could easily confuse with this one.

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?

'Applies when the user asks to change voice, posting times, review mode, auto-reply or content rules' gives a clear triggering context, and the dry_run note adds a safe-preview path. It stops short of naming alternatives or exclusions (e.g., when to use apply_account_settings or preview_account_settings instead).

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.