Skip to main content
Glama
Sign In
MCP Google Multi-Account Server

MCP Google Multi-Account Server

by bkbaheti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

google_set_account_description

Assign a human-readable label to a Google account so you can distinguish it in account listings. Set an empty string to remove the label.

Instructions

Set a human-readable description on a Google account (e.g., "Work - engineering team", "Personal Gmail"). This description appears in google_list_accounts output to help identify accounts. Set to empty string to remove.

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": {
      "accountId": "<accountId>",
      "description": "<description>"
    },
    "name": "google_set_account_description"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdYesThe account ID, alias, or email to update
descriptionYesHuman-readable description (e.g., "Work - engineering team"). Empty string to remove.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.3

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses meaningful behaviors: the description appears in google_list_accounts, and setting to an empty string removes it. This goes beyond the schema and helps an agent understand side effects, though it does not mention overwrite behavior or auth requirements.

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?

Two sentences with no fluff. The first sentence states the action with examples; the second gives context and removal semantics. Every word is useful and front-loaded.

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 simple 2-parameter setter with no output schema and no annotations, the description is complete: it states what it does, where the effect appears, and how to unset. Enough for an agent to select and invoke correctly without further detail.

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% for both parameters. The description adds only redundant examples and the empty-string removal note, which is already in the schema. It adds no new parameter-specific semantics beyond what the schema provides.

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?

The description uses a specific verb ('Set') and resource ('human-readable description on a Google account'), with examples and a clear distinction from sibling tools like google_set_account_labels or google_set_account_alias. It states exactly what the tool does and where the effect is visible (google_list_accounts output).

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?

The description provides context on when to use this tool (to help identify accounts in google_list_accounts) and how to remove a description, but it does not explicitly compare or exclude alternatives like labels or alias. Clear context, though no direct 'when not to use'.

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

Deploy Server

Other Tools