Skip to main content
Glama

pylon_create_tag

Create custom tags to categorize and organize accounts, contacts, or issues within the Pylon customer support platform.

Instructions

Create a new tag

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYesThe tag name/value
object_typeYesType of object this tag applies to
hex_colorNoHex color code for the tag (e.g., #FF5733)

Implementation Reference

  • src/index.ts:530-549 (registration)
    Registration of the MCP tool 'pylon_create_tag' including input schema and handler function that delegates to PylonClient.
    server.tool(
    	'pylon_create_tag',
    	'Create a new tag',
    	{
    		value: z.string().describe('The tag name/value'),
    		object_type: z
    			.enum(['account', 'issue', 'contact'])
    			.describe('Type of object this tag applies to'),
    		hex_color: z
    			.string()
    			.optional()
    			.describe('Hex color code for the tag (e.g., #FF5733)'),
    	},
    	async (params) => {
    		const result = await client.createTag(params);
    		return {
    			content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }],
    		};
    	},
    );
  • MCP tool handler for pylon_create_tag: calls PylonClient.createTag and formats response.
    async (params) => {
    	const result = await client.createTag(params);
    	return {
    		content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }],
    	};
    },
  • Zod input schema for pylon_create_tag tool.
    {
    	value: z.string().describe('The tag name/value'),
    	object_type: z
    		.enum(['account', 'issue', 'contact'])
    		.describe('Type of object this tag applies to'),
    	hex_color: z
    		.string()
    		.optional()
    		.describe('Hex color code for the tag (e.g., #FF5733)'),
    },
  • PylonClient.createTag method: performs POST request to /tags API endpoint.
    async createTag(data: {
    	value: string;
    	object_type: 'account' | 'issue' | 'contact';
    	hex_color?: string;
    }): Promise<SingleResponse<Tag>> {
    	return this.request<SingleResponse<Tag>>('POST', '/tags', data);
    }
  • TypeScript interface for Tag object used in createTag response.
    export interface Tag {
    	id: string;
    	value: string;
    	object_type: 'account' | 'issue' | 'contact';
    	hex_color?: 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 for behavioral disclosure. 'Create a new tag' implies a write operation but doesn't specify permissions needed, whether tags are unique, what happens on duplicate values, or error conditions. 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 extremely concise at three words, front-loaded with the core action, and contains no wasted language. Every word earns its place by directly stating the tool's function.

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 no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns, error handling, or behavioral constraints, leaving the agent with incomplete operational context despite good schema coverage.

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 parameters are fully documented in the schema. The description adds no additional meaning about parameters beyond implying creation involves some input values. 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.

Purpose4/5

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

The description clearly states the action ('Create') and resource ('a new tag'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like pylon_update_tag or pylon_delete_tag, which would require mentioning it's for initial creation rather than modification or removal.

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 provides no guidance on when to use this tool versus alternatives. With siblings like pylon_update_tag and pylon_get_tag available, there's no indication of prerequisites, appropriate contexts, or distinctions between creation and other tag operations.

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