Skip to main content
Glama

Update your answering-line settings

update_answering_line
Destructive

Save supported owner-console settings on one answering line you own. Use after the owner approves the changes; get_answering_line supplies line_id. Only supplied fields change: hours, greeting, services, price_ranges, extra_instructions, notification email, stopping texts, on-call transfer number and appointment length. The same validation, settings lease, calendar updates and guarded agent rebuild as the owner console apply; protected instructions may wait for review and a saved change may still await agent sync, as the result explains. This does not change the business name, address, billing, owner identity, SMS destination or enable texts; use pause_answering_line or resume_answering_line to change answering status. close_answering_line ends answering and keeps the unused balance recorded. For history use get_line_calls/get_line_messages, or get_line_call_transcript for one call. Needs lines:manage; rate limited per account and line. Returns saved, message, warning and any existing bookings on newly closed days.

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": {
      "line_id": "<line_id>",
      "settings": "<settings>"
    },
    "name": "update_answering_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
line_idYesAn owned line_id from get_answering_line.
settingsYesOnly these owner-editable fields are accepted; omitted values remain unchanged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag a destructive, non-idempotent write, and the description goes well beyond them: only supplied fields change, the same validation/lease/calendar/agent-rebuild path as the console applies, protected instructions may be held for review, and a save may still await agent sync. It adds the lines:manage permission, per-account and per-line rate limits, and the return payload (saved, message, warning, bookings on newly closed days).

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?

Front-loaded with the action and precondition, then scope, side effects, and routing in a logical order. It is dense but each sentence carries information; the trailing history-routing sentence is the one element that is slightly tangential for an update tool.

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

Completeness5/5

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

For a nested-schema mutation with no output schema, the description covers the gaps that matter: permissions, rate limits, asynchronous review/sync states, side effects on calendars and bookings, and the shape of the result. An agent has everything needed to call it correctly and interpret the outcome.

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 100%, so the schema carries the field-level detail and the baseline would be 3. The description nonetheless adds real meaning: it enumerates the accepted settings and states the partial-update rule ('Only supplied fields change') plus the explicit exclusion list (business name, address, billing, owner identity, SMS destination, enabling texts), which clarifies why certain fields are absent.

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?

Opens with a specific verb and resource: 'Save supported owner-console settings on one answering line you own.' It scopes the operation (only owner-editable fields) and implicitly distinguishes itself from set_up_answering_line and get_answering_line, so an agent knows this is a partial update on an existing line.

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

Usage Guidelines5/5

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

Explicitly states the precondition ('Use after the owner approves the changes') and the source of the required identifier ('get_answering_line supplies line_id'). It also names alternatives and when to use them: pause/resume for answering status, close_answering_line to end answering, get_line_calls/get_line_messages/get_line_call_transcript for history.

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.