Skip to main content
Glama

pylon_list_accounts

Retrieve all customer accounts from the Pylon support platform with pagination controls to manage large datasets efficiently.

Instructions

List all accounts in Pylon with optional pagination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of accounts to return (1-1000, default 100)
cursorNoPagination cursor for next page

Implementation Reference

  • src/index.ts:42-60 (registration)
    Registers the pylon_list_accounts tool with MCP server, including input schema (limit, cursor) and handler that calls PylonClient.listAccounts and returns JSON-formatted response.
    server.tool(
    	'pylon_list_accounts',
    	'List all accounts in Pylon with optional pagination',
    	{
    		limit: z
    			.number()
    			.min(1)
    			.max(1000)
    			.optional()
    			.describe('Number of accounts to return (1-1000, default 100)'),
    		cursor: z.string().optional().describe('Pagination cursor for next page'),
    	},
    	async ({ limit, cursor }) => {
    		const result = await client.listAccounts({ limit, cursor });
    		return {
    			content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
    		};
    	},
    );
  • Inline handler function for the pylon_list_accounts tool, which invokes the PylonClient.listAccounts method with provided parameters and serializes the result.
    async ({ limit, cursor }) => {
    	const result = await client.listAccounts({ limit, cursor });
    	return {
    		content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
    	};
    },
  • Zod schema defining optional input parameters 'limit' (1-1000) and 'cursor' for pagination in pylon_list_accounts tool.
    {
    	limit: z
    		.number()
    		.min(1)
    		.max(1000)
    		.optional()
    		.describe('Number of accounts to return (1-1000, default 100)'),
    	cursor: z.string().optional().describe('Pagination cursor for next page'),
    },
  • PylonClient.listAccounts helper method that constructs the API GET request to /accounts with pagination query parameters and returns paginated list of accounts.
    async listAccounts(
    	params?: PaginationParams,
    ): Promise<PaginatedResponse<Account>> {
    	const searchParams = new URLSearchParams();
    	if (params?.limit) searchParams.set('limit', params.limit.toString());
    	if (params?.cursor) searchParams.set('cursor', params.cursor);
    	const query = searchParams.toString();
    	return this.request<PaginatedResponse<Account>>(
    		'GET',
    		`/accounts${query ? `?${query}` : ''}`,
    	);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions pagination behavior, which is useful, but doesn't cover other important aspects like rate limits, authentication requirements, response format, or whether this is a read-only operation (though implied by 'list'). For a list tool with zero annotation coverage, this leaves significant gaps.

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 that communicates the core functionality upfront. Every word earns its place with no wasted text or unnecessary elaboration.

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

Completeness3/5

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

For a list tool with 2 parameters and 100% schema coverage but no annotations or output schema, the description provides basic functionality but lacks important context. It doesn't explain what information is returned about accounts, how results are ordered, or other behavioral details that would help an agent use it effectively.

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?

The description mentions 'optional pagination' which aligns with the 'cursor' parameter in the schema, but doesn't add meaningful semantic context beyond what the 100% schema coverage already provides. The schema descriptions clearly explain both parameters, so the baseline 3 is appropriate.

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 clearly states the action ('List all accounts') and resource ('in Pylon'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'pylon_search_accounts' or 'pylon_get_account', which would require a 5.

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?

The description mentions 'optional pagination' which provides some context about usage, but doesn't specify when to use this tool versus alternatives like 'pylon_search_accounts' or 'pylon_get_account'. No explicit guidance on when-not-to-use or prerequisites is provided.

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