Skip to main content
Glama

pylon_search_contacts

Search contacts in Pylon customer support platform using filters like ID, email, or account ID to find specific customer records.

Instructions

Search contacts with filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterYesFilter object with fields like id, email, account_id. Supports operators: equals, in, not_in, string_contains
limitNoResults limit
cursorNoPagination cursor

Implementation Reference

  • src/index.ts:259-282 (registration)
    Registers the MCP tool 'pylon_search_contacts' with Zod input schema (filter, limit, cursor) and handler function that invokes PylonClient.searchContacts and formats the response as text.
    server.tool(
    	'pylon_search_contacts',
    	'Search contacts with filters',
    	{
    		filter: z
    			.object({
    				id: z.object({}).optional(),
    				email: z.object({}).optional(),
    				account_id: z.object({}).optional(),
    			})
    			.passthrough()
    			.describe(
    				'Filter object with fields like id, email, account_id. Supports operators: equals, in, not_in, string_contains',
    			),
    		limit: z.number().min(1).max(1000).optional().describe('Results limit'),
    		cursor: z.string().optional().describe('Pagination cursor'),
    	},
    	async ({ filter, limit, cursor }) => {
    		const result = await client.searchContacts(filter, { limit, cursor });
    		return {
    			content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
    		};
    	},
    );
  • The execution handler for the tool, which calls the PylonClient's searchContacts method and returns the result as a JSON-formatted text content block.
    async ({ filter, limit, cursor }) => {
    	const result = await client.searchContacts(filter, { limit, cursor });
    	return {
    		content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
    	};
    },
  • Zod schema defining the input parameters: filter (object with optional id/email/account_id), limit (1-1000), cursor (string).
    {
    	filter: z
    		.object({
    			id: z.object({}).optional(),
    			email: z.object({}).optional(),
    			account_id: z.object({}).optional(),
    		})
    		.passthrough()
    		.describe(
    			'Filter object with fields like id, email, account_id. Supports operators: equals, in, not_in, string_contains',
    		),
    	limit: z.number().min(1).max(1000).optional().describe('Results limit'),
    	cursor: z.string().optional().describe('Pagination cursor'),
    },
  • PylonClient helper method that performs the actual API request (POST /contacts/search) with filter, limit, and cursor parameters.
    async searchContacts(
    	filter: object,
    	params?: PaginationParams,
    ): Promise<PaginatedResponse<Contact>> {
    	return this.request<PaginatedResponse<Contact>>(
    		'POST',
    		'/contacts/search',
    		{
    			filter,
    			limit: params?.limit,
    			cursor: params?.cursor,
    		},
    	);
    }
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. It mentions 'filters' but doesn't disclose behavioral traits like pagination behavior (implied by 'cursor' parameter), rate limits, authentication needs, or what happens on no matches. For a search tool with no annotation coverage, this is a significant gap in transparency.

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, clearly stating the core function without unnecessary elaboration.

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 no annotations, no output schema, and a search tool with filtering and pagination complexity, the description is incomplete. It lacks details on return format, error handling, or behavioral context, making it inadequate for an agent to fully understand tool usage.

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 parameters (filter, limit, cursor). The description adds minimal value by mentioning 'filters' but doesn't provide additional semantics beyond what's in the schema descriptions (e.g., operators for filter). Baseline 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.

Purpose3/5

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

The description 'Search contacts with filters' clearly states the action (search) and resource (contacts), but it's vague about scope and doesn't differentiate from sibling tools like 'pylon_list_contacts' or 'pylon_get_contact'. It specifies 'with filters' which adds some specificity but remains general.

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 like 'pylon_list_contacts' or 'pylon_get_contact'. The description implies filtering capability but doesn't specify use cases, prerequisites, or exclusions, leaving the agent without contextual direction.

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