Skip to main content
Glama

pylon_delete_account

Remove a customer account from the Pylon support platform by providing the account ID to delete user data and records.

Instructions

Delete an account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe account ID to delete

Implementation Reference

  • src/index.ts:121-133 (registration)
    Registration of the 'pylon_delete_account' MCP tool, including description, input schema (account ID), and inline handler that calls PylonClient.deleteAccount and returns JSON-formatted result.
    server.tool(
    	'pylon_delete_account',
    	'Delete an account',
    	{
    		id: z.string().describe('The account ID to delete'),
    	},
    	async ({ id }) => {
    		const result = await client.deleteAccount(id);
    		return {
    			content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
    		};
    	},
    );
  • Inline handler function executing the tool logic: deletes the account via client and returns response.
    async ({ id }) => {
    	const result = await client.deleteAccount(id);
    	return {
    		content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
    	};
    },
  • Zod input schema defining the required 'id' parameter.
    {
    	id: z.string().describe('The account ID to delete'),
    },
  • PylonClient.deleteAccount method: performs authenticated DELETE request to Pylon API endpoint /accounts/{id}.
    async deleteAccount(
    	id: string,
    ): Promise<SingleResponse<{ success: boolean }>> {
    	return this.request<SingleResponse<{ success: boolean }>>(
    		'DELETE',
    		`/accounts/${id}`,
    	);
    }
  • Private request method in PylonClient used for all API calls, handling authentication, fetch, error handling, and JSON parsing.
    private async request<T>(
    	method: string,
    	path: string,
    	body?: object,
    ): Promise<T> {
    	const url = `${PYLON_API_BASE}${path}`;
    	const headers: Record<string, string> = {
    		Authorization: `Bearer ${this.apiToken}`,
    		'Content-Type': 'application/json',
    		Accept: 'application/json',
    	};
    
    	const response = await fetch(url, {
    		method,
    		headers,
    		body: body ? JSON.stringify(body) : undefined,
    	});
    
    	if (!response.ok) {
    		const errorText = await response.text();
    		throw new Error(
    			`Pylon API error: ${response.status} ${response.statusText} - ${errorText}`,
    		);
    	}
    
    	return response.json() as Promise<T>;
    }
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. 'Delete an account' implies a destructive, irreversible operation, but it doesn't disclose behavioral traits such as permissions required, confirmation steps, side effects (e.g., cascading deletions), rate limits, or error handling. This leaves significant gaps for a mutation tool.

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 ('Delete an account') that is front-loaded and wastes no words. It's appropriately sized for a simple operation, earning full marks for conciseness.

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?

Given the tool's complexity (destructive mutation), lack of annotations, and no output schema, the description is incomplete. It doesn't cover critical aspects like what happens post-deletion, return values, or error cases. For a delete operation, this minimal description is inadequate to ensure safe and correct usage.

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?

The input schema has 1 parameter with 100% description coverage ('The account ID to delete'), so the schema fully documents the parameter. The description adds no extra meaning beyond the schema, but with 0 parameters needing compensation, the baseline is 4 as per rules for minimal parameter burden.

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 'Delete an account' states a clear verb ('Delete') and resource ('account'), but it's vague about scope and doesn't distinguish from siblings like pylon_delete_contact or pylon_delete_issue. It doesn't specify what type of account (e.g., user, system) or context, making it minimally adequate but lacking specificity.

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. It doesn't mention prerequisites (e.g., account must exist), exclusions (e.g., cannot delete if active), or sibling tools like pylon_update_account for modifications. The description offers no context for usage decisions.

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