Skip to main content
Glama

update_application

DestructiveIdempotent

Update application-level settings (name, active state, default language, language for everyone else, incoming-message behavior, the member notice when AI credits run out). Requires the manage_settings permission in that application. Only the fields you pass are changed; omitted fields keep their current value, so the call is idempotent. Returns the updated application.

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

Input Schema

NameRequiredDescriptionDefault
nameNoNew display name. Omit to leave unchanged.
isActiveNoSet false to deactivate the application — its bots stop responding. Omit to leave unchanged.
applicationIdNoApplication (workspace) id. Optional: an application-scoped key (app_...) defaults to its own application, but a personal key (usr_...) has no default and omitting it fails with MCP_APPLICATION_REQUIRED. Call list_applications to get the id.
defaultLanguageNoNew default language. It is the SOURCE language of the application's content: every block text is taken to be written in it, and translations are made from it. Any ISO 639 base language tag is accepted and normalised to its lowercase base form ("de", "pt-BR" → "pt"); a value that is not a 2-3 letter tag (for example "german") is rejected with INVALID_LANGUAGE — nothing falls back to "en". Changing it translates NOTHING: the texts already written are simply treated as written in the new language from then on, and the new default is dropped from the list of additional languages. Omit to leave unchanged.
fallbackLanguageNoLanguage for everyone else: the content language a contact gets when their own language is not one of the bot's languages (or unknown). Must be the default language or an enabled language; "" resets to the default language. Omit to leave unchanged.
aiUnavailableNoticesNoThe bot's "assistant unavailable" notice per language, e.g. { "it": "L'assistente non è disponibile al momento. Riprova più tardi." }: the one short sentence a member gets when an AI step is refused because the owner's AI credits ran out. Every language of the bot (default language + additional languages) needs one, written in that language; en, ru and es have a platform text. The result lists aiUnavailableNoticeMissingLanguages. Only the languages you pass change; "" removes one. Omit to leave unchanged.
incomingMessageFlowIdNoFlow of this application to run for unmatched inbound messages. Required when incomingMessageBehavior is EXECUTE_FLOW.
incomingMessageBehaviorNoWhat happens to an inbound message that matches no trigger: LIVE_CHAT routes it to a human operator, EXECUTE_FLOW runs the flow named by incomingMessageFlowId. Side effect of EXECUTE_FLOW: the platform also adds an "any message" MESSAGE trigger with originModuleKey "incoming_message_behavior" to that flow's start block, and removes it when this setting moves to another flow or back to LIVE_CHAT. It is system-owned: when you later resend that block's triggers with update_block, resend it unchanged with its id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / aiUnavailableNotices
      Added value: +{
      +  "additionalProperties": {
      +    "type": "string"
      +  },
      +  "description": "The bot's \"assistant unavailable\" notice per language, e.g. { \"it\": \"L'assistente non è disponibile al momento. Riprova più tardi.\" }: the one short sentence a member gets when an AI step is refused because the owner's AI credits ran out. Every language of the bot (default language + additional languages) needs one, written in that language; en, ru and es have a platform text. The result lists aiUnavailableNoticeMissingLanguages. Only the languages you pass change; \"\" removes one. Omit to leave unchanged.",
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / incomingMessageFlowId / description
      Previous value: -"Flow to run for unmatched inbound messages. Required in practice when incomingMessageBehavior is EXECUTE_FLOW."New value: +"Flow of this application to run for unmatched inbound messages. Required when incomingMessageBehavior is EXECUTE_FLOW."
  3. Changed2 schema fields changed
    • changedInput schema / properties / defaultLanguage / description
      Previous value: -"Default language for new flows. Only \"en\", \"ru\", and \"es\" are supported; any other value falls back to \"en\"."New value: +"New default language. It is the SOURCE language of the application's content: every block text is taken to be written in it, and translations are made from it. Any ISO 639 base language tag is accepted and normalised to its lowercase base form (\"de\", \"pt-BR\" → \"pt\"); a value that is not a 2-3 letter tag (for example \"german\") is rejected with INVALID_LANGUAGE — nothing falls back to \"en\". Changing it translates NOTHING: the texts already written are simply treated as written in the new language from then on, and the new default is dropped from the list of additional languages. Omit to leave unchanged."
    • changedInput schema / properties / incomingMessageBehavior / description
      Previous value: -"What happens to an inbound message that matches no trigger: LIVE_CHAT routes it to a human operator, EXECUTE_FLOW runs the flow named by incomingMessageFlowId."New value: +"What happens to an inbound message that matches no trigger: LIVE_CHAT routes it to a human operator, EXECUTE_FLOW runs the flow named by incomingMessageFlowId. Side effect of EXECUTE_FLOW: the platform also adds an \"any message\" MESSAGE trigger with originModuleKey \"incoming_message_behavior\" to that flow's start block, and removes it when this setting moves to another flow or back to LIVE_CHAT. It is system-owned: when you later resend that block's triggers with update_block, resend it unchanged with its id."
  4. Changed1 schema field changed
    • addedInput schema / properties / fallbackLanguage
      Added value: +{
      +  "description": "Language for everyone else: the content language a contact gets when their own language is not one of the bot's languages (or unknown). Must be the default language or an enabled language; \"\" resets to the default language. Omit to leave unchanged.",
      +  "type": "string"
      +}
  5. Changed6 schema fields changed
    • addedInput schema / properties / applicationId / description
      Added value: +"Application (workspace) id. Optional: an application-scoped key (app_...) defaults to its own application, but a personal key (usr_...) has no default and omitting it fails with MCP_APPLICATION_REQUIRED. Call list_applications to get the id."
    • addedInput schema / properties / defaultLanguage / description
      Added value: +"Default language for new flows. Only \"en\", \"ru\", and \"es\" are supported; any other value falls back to \"en\"."
    • addedInput schema / properties / incomingMessageBehavior / description
      Added value: +"What happens to an inbound message that matches no trigger: LIVE_CHAT routes it to a human operator, EXECUTE_FLOW runs the flow named by incomingMessageFlowId."
    • addedInput schema / properties / incomingMessageFlowId / description
      Added value: +"Flow to run for unmatched inbound messages. Required in practice when incomingMessageBehavior is EXECUTE_FLOW."
    • addedInput schema / properties / isActive / description
      Added value: +"Set false to deactivate the application — its bots stop responding. Omit to leave unchanged."
    • addedInput schema / properties / name / description
      Added value: +"New display name. Omit to leave unchanged."
  6. Added

TDQS

A4/5.0
Behavior3/5

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

The description adds the permission requirement and the partial-update/idempotent contract, but "so the call is idempotent" merely restates idempotentHint=true already in annotations. With destructiveHint=true declared, the description never warns what the destructive path is (e.g. setting isActive=false stops bots responding, changing defaultLanguage silently reinterprets existing texts) — that risk detail lives only in the parameter schema.

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

Conciseness5/5

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

Three sentences with zero waste: capability first, permission requirement second, mutation semantics and return value third. Nothing is buried and nothing repeats the parameter list verbatim.

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 an 8-parameter, all-optional tool with a nested object and no output schema, the definition covers permission, partial-update semantics, and confirms a return value ("the updated application"). It does not describe the returned payload or the aiUnavailableNoticeMissingLanguages outcome, but the latter is documented in the schema, so the remaining gap is minor.

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 per-parameter meaning is already fully carried by the schema, including the EXECUTE_FLOW side effect and the aiUnavailableNotices per-language rules. The description only names the settable fields in prose, which adds association but no semantics beyond the schema — baseline 3.

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 ("Update application-level settings") and then enumerates the exact settings in scope: name, active state, default language, fallback language, incoming-message behavior, and AI-credit notice. An agent can tell this apart from create_application/deploy_application without opening the schema.

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 the prerequisite ("Requires the manage_settings permission in that application") and the partial-update contract ("Only the fields you pass are changed; omitted fields keep their current value"), which is real call-shaping context. It stops short of explicitly naming when a sibling such as deploy_application is the right call instead, so there is no true alternative routing.

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.