Skip to main content
Glama

update_settings

Modify workspace preferences including language, article length, picture style, tone, auto-accept suggestions, and writing style settings for content generation.

Instructions

Update workspace settings: language, article length, pictures style, tone, auto-accept suggestions, writing style preferences, and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspace_idYesWorkspace UUID
languageNoLanguage code, e.g. en, fr
article_lengthNoDefault article length: short, normal, long, extra_long
pictures_styleNoDefault picture style
max_articles_per_periodNoMax articles per period
max_articles_periodNoPeriod: day, week, month
prefered_tone_of_voice_idNoDefault tone of voice UUID
auto_accept_suggestionsNoAutomatically accept new suggestions
use_title_cases_in_headingsNoUse title case in article headings
prefer_active_voiceNoPrefer active voice in articles
write_in_first_personNoWrite articles in first person

Implementation Reference

  • The `update_settings` tool is registered and implemented within `src/tools/settings.ts`. It takes a workspace ID and various optional configuration parameters, which it then merges into a PATCH request to the workspace settings endpoint.
    server.tool(
      'update_settings',
      'Update workspace settings: language, article length, pictures style, tone, auto-accept suggestions, writing style preferences, and more.',
      {
        workspace_id: z.string().describe('Workspace UUID'),
        language: z.string().optional().describe('Language code, e.g. en, fr'),
        article_length: z.string().optional().describe('Default article length: short, normal, long, extra_long'),
        pictures_style: z.string().optional().describe('Default picture style'),
        max_articles_per_period: z.number().optional().describe('Max articles per period'),
        max_articles_period: z.string().optional().describe('Period: day, week, month'),
        prefered_tone_of_voice_id: z.string().optional().describe('Default tone of voice UUID'),
        auto_accept_suggestions: z.boolean().optional().describe('Automatically accept new suggestions'),
        use_title_cases_in_headings: z.boolean().optional().describe('Use title case in article headings'),
        prefer_active_voice: z.boolean().optional().describe('Prefer active voice in articles'),
        write_in_first_person: z.boolean().optional().describe('Write articles in first person'),
      },
      async ({ workspace_id, ...params }) => {
        const body: Record<string, unknown> = {};
        for (const [k, v] of Object.entries(params)) {
          if (v !== undefined) body[k] = v;
        }
        const res = await client.patch(`/workspaces/${workspace_id}/settings`, { settings: body });
        return { content: [{ type: 'text' as const, text: JSON.stringify(res.data) }] };
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Update' implies a mutation operation, the description doesn't address critical behavioral aspects: whether this requires specific permissions, if changes are reversible, what happens to unspecified settings, potential side effects, or error conditions. For a mutation tool with 11 parameters and no annotation coverage, this is a significant gap.

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?

The description is a single, efficient sentence that front-loads the core purpose ('Update workspace settings') followed by illustrative examples. There's no wasted verbiage, though the 'and more' could be slightly more precise. The structure is clear and direct.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (mutation operation with 11 parameters), lack of annotations, and absence of an output schema, the description is minimally adequate but incomplete. It identifies the tool's purpose and some example parameters but omits behavioral context, usage guidance, and output expectations. For a settings mutation tool, more comprehensive disclosure would be beneficial.

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 11 parameters thoroughly. The description lists some example parameters (language, article length, pictures style, tone, auto-accept suggestions, writing style preferences) but adds no additional semantic context beyond what's in the schema. This meets the baseline of 3 when schema coverage is high.

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 clearly states the tool's purpose: 'Update workspace settings' followed by a non-exhaustive list of specific settings that can be modified (language, article length, pictures style, tone, auto-accept suggestions, writing style preferences). It uses a specific verb ('Update') and identifies the resource ('workspace settings'), though it doesn't explicitly differentiate from the sibling 'update_workspace' tool.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention the sibling 'update_workspace' tool, nor does it indicate prerequisites, constraints, or appropriate contexts for use. The agent must infer usage from the tool name and description alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hirebalzac/mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server