Skip to main content
Glama

pylon_update_account

Modify account details in the Pylon customer support platform by updating name, domains, owner, tags, or logo.

Instructions

Update an existing account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe account ID
nameNoNew name for the account
domainsNoUpdated list of domains
primary_domainNoUpdated primary domain
logo_urlNoUpdated logo URL
owner_idNoUpdated owner ID
tagsNoUpdated tags

Implementation Reference

  • src/index.ts:101-119 (registration)
    Registration of the 'pylon_update_account' tool with input schema and handler function that delegates to PylonClient.updateAccount
    server.tool(
    	'pylon_update_account',
    	'Update an existing account',
    	{
    		id: z.string().describe('The account ID'),
    		name: z.string().optional().describe('New name for the account'),
    		domains: z.array(z.string()).optional().describe('Updated list of domains'),
    		primary_domain: z.string().optional().describe('Updated primary domain'),
    		logo_url: z.string().optional().describe('Updated logo URL'),
    		owner_id: z.string().optional().describe('Updated owner ID'),
    		tags: z.array(z.string()).optional().describe('Updated tags'),
    	},
    	async ({ id, ...data }) => {
    		const result = await client.updateAccount(id, data);
    		return {
    			content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }],
    		};
    	},
    );
  • MCP tool handler for pylon_update_account, which calls the PylonClient and formats the response
    async ({ id, ...data }) => {
    	const result = await client.updateAccount(id, data);
    	return {
    		content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }],
    	};
    },
  • Zod input schema for the pylon_update_account tool parameters
    	id: z.string().describe('The account ID'),
    	name: z.string().optional().describe('New name for the account'),
    	domains: z.array(z.string()).optional().describe('Updated list of domains'),
    	primary_domain: z.string().optional().describe('Updated primary domain'),
    	logo_url: z.string().optional().describe('Updated logo URL'),
    	owner_id: z.string().optional().describe('Updated owner ID'),
    	tags: z.array(z.string()).optional().describe('Updated tags'),
    },
  • PylonClient.updateAccount method that makes the PATCH API request to update an account
    async updateAccount(
    	id: string,
    	data: Partial<Account>,
    ): Promise<SingleResponse<Account>> {
    	return this.request<SingleResponse<Account>>(
    		'PATCH',
    		`/accounts/${id}`,
    		data,
    	);
    }
  • TypeScript interface for Account used in updateAccount parameters and response
    export interface Account {
    	id: string;
    	name: string;
    	domains?: string[];
    	primary_domain?: string;
    	logo_url?: string;
    	owner_id?: string;
    	channels?: object[];
    	custom_fields?: object;
    	external_ids?: object[];
    	tags?: string[];
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Update an existing account' implies a mutation operation, but it doesn't disclose behavioral traits like permission requirements, whether updates are partial or complete, what happens to unspecified fields, rate limits, or error conditions. This is inadequate for a mutation tool with zero annotation coverage.

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?

The description is a single, efficient sentence with zero waste. It's appropriately sized and front-loaded, though it could benefit from more detail 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?

For a mutation tool with 7 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns, error handling, or behavioral context. The agent lacks sufficient information to use this tool effectively beyond basic parameter mapping.

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 the schema already documents all 7 parameters with clear descriptions. The description adds no additional meaning beyond what's in the schema (e.g., it doesn't explain relationships between parameters like domains and primary_domain). Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update an existing account' clearly states the action (update) and resource (account), but it's vague about what specifically gets updated. It doesn't distinguish this tool from sibling update tools like pylon_update_contact or pylon_update_issue, which follow the same pattern.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites (like needing an account ID), when not to use it, or how it differs from other update operations in the sibling tool list.

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/JustinBeckwith/pylon-mcp'

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