Skip to main content
Glama

linear_updateCustomer

Idempotent

Update a customer's name, size, revenue, tier, domains, or integrations. Provide the customer ID to modify any attribute.

Instructions

Update a customer

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCustomer ID
nameNoCustomer name
sizeNoCustomer employee or seat count
tierIdNoCustomer tier ID
domainsNoCustomer email domains
logoUrlNoCustomer logo URL
ownerIdNoOwner user ID
revenueNoAnnual customer revenue
statusIdNoCustomer status ID
externalIdsNoExternal system IDs
mainSourceIdNoPrimary external source ID
slackChannelIdNoLinked Slack channel ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
urlNo
nameNo
sizeNo
tierNo
ownerNo
slugIdNo
statusNo
domainsNo
logoUrlNo
revenueNo
createdAtNo
updatedAtNo
archivedAtNo
externalIdsNo
mainSourceIdNo
slackChannelIdNo
approximateNeedCountNo
Behavior2/5

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, idempotentHint=true. The description adds no behavioral context such as required permissions or effect on existing data.

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 extremely concise, but arguably too minimal. It could include more detail without being verbose.

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?

With 12 parameters and an output schema (not shown), the description provides no information about return values, required state, or side effects, leaving the agent underinformed for a tool of this complexity.

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 baseline is 3. The description does not add any extra meaning to parameters beyond their schema descriptions.

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 a customer' clearly states the verb and resource, and distinguishes it from siblings like create or delete. However, it could be more specific about which fields are updatable, but the schema provides that detail.

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 on when to use this tool versus alternatives like createCustomer or deleteCustomer. No prerequisites or context about when updates are appropriate.

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/tacticlaunch/mcp-linear'

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