Skip to main content
Glama

update_account

Idempotent

Update an account's name, email, phone, labels, custom fields, and address by providing the account ID and required details.

Instructions

Update an account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the account to update
nameYesArbitrary string representing the name of the account. Is autogenerated for personal accounts.
emailNoA string representing the billing e-mail of the account
phoneNoA string representing the phone number of the account
label_idsNoIDs of the labels
customNoThe custom properties of the account.
address_attributesNo
Behavior2/5

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

The description only states the action; it does not add behavioral context beyond what annotations already provide (idempotentHint=true, destructiveHint=false). No mention of effects on existing data or response behavior.

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 description is a single sentence, concise but overly minimal. It is front-loaded but does not fully earn its place given the tool's complexity.

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

Completeness2/5

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

No output schema exists, yet the description does not clarify return values or confirm successful update. With 7 parameters including nested objects, more context is needed.

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 high (86%), so the schema already documents parameters. The description adds no additional parameter information, keeping it at baseline.

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 'Update an account' clearly indicates the action and resource. It is distinct from create_account and get_account among siblings, but does not differentiate from other update tools.

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?

No guidance is provided on when to use this tool versus alternatives, nor any restrictions or prerequisites beyond the required parameters in the schema.

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/martijnpieters/eduframe-mcp'

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