Skip to main content
Glama

pylon_list_contacts

Retrieve and manage contact lists from Pylon customer support platform with pagination controls for efficient data handling.

Instructions

List all contacts in Pylon with optional pagination

Input Schema

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

Implementation Reference

  • src/index.ts:165-183 (registration)
    Registers the 'pylon_list_contacts' MCP tool, including description, Zod input schema for pagination, and handler function that invokes PylonClient.listContacts and formats the response as text content.
    server.tool(
    	'pylon_list_contacts',
    	'List all contacts in Pylon with optional pagination',
    	{
    		limit: z
    			.number()
    			.min(1)
    			.max(1000)
    			.optional()
    			.describe('Number of contacts to return (1-1000, default 100)'),
    		cursor: z.string().optional().describe('Pagination cursor for next page'),
    	},
    	async ({ limit, cursor }) => {
    		const result = await client.listContacts({ limit, cursor });
    		return {
    			content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
    		};
    	},
    );
  • The core handler function for the tool, which calls the client's listContacts method and returns the JSON-stringified result as MCP content.
    async ({ limit, cursor }) => {
    	const result = await client.listContacts({ limit, cursor });
    	return {
    		content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
    	};
    },
  • Zod schema defining the input parameters for the tool: optional limit (1-1000) and cursor for pagination.
    {
    	limit: z
    		.number()
    		.min(1)
    		.max(1000)
    		.optional()
    		.describe('Number of contacts to return (1-1000, default 100)'),
    	cursor: z.string().optional().describe('Pagination cursor for next page'),
    },
  • PylonClient.listContacts method: constructs query params for limit and cursor, makes GET request to /contacts endpoint, returns paginated list of contacts.
    async listContacts(
    	params?: PaginationParams,
    ): Promise<PaginatedResponse<Contact>> {
    	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<Contact>>(
    		'GET',
    		`/contacts${query ? `?${query}` : ''}`,
    	);
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'optional pagination,' which adds some context beyond the input schema, but fails to describe critical behaviors such as whether this is a read-only operation, what permissions are required, rate limits, or the structure of returned data. For a list tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 front-loads the core purpose ('List all contacts in Pylon') and adds a key feature ('with optional pagination') without any wasted words. Every part of the description earns its place, making it easy to scan and understand quickly.

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?

Given the tool's complexity (a list operation with pagination), no annotations, and no output schema, the description is minimally adequate but incomplete. It covers the basic purpose and hints at pagination, but lacks details on behavioral traits, return values, or error handling. For a tool with 2 parameters and 100% schema coverage, it meets the baseline but doesn't fully compensate for the missing annotation and output context.

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 input schema has 100% description coverage, with clear documentation for 'limit' and 'cursor' parameters. The description adds minimal value by mentioning 'optional pagination,' which aligns with the schema but doesn't provide additional semantics like how pagination works in practice or default behaviors. Given the high schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

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 verb ('List') and resource ('all contacts in Pylon'), making the purpose immediately understandable. It distinguishes this tool from sibling tools like 'pylon_get_contact' (which retrieves a single contact) and 'pylon_search_contacts' (which performs filtered searches). However, it doesn't explicitly differentiate from 'pylon_list_accounts' or 'pylon_list_issues' in terms of resource type beyond the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context through 'optional pagination,' suggesting this is for retrieving multiple contacts. However, it doesn't explicitly state when to use this versus alternatives like 'pylon_search_contacts' (for filtered searches) or 'pylon_get_contact' (for single contacts), nor does it mention prerequisites or exclusions. The guidance is implied but not comprehensive.

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