Skip to main content
Glama

pylon_get_tag

Retrieve a specific tag by its ID from the Pylon customer support platform for management and organization purposes.

Instructions

Get a specific tag by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe tag ID

Implementation Reference

  • src/index.ts:516-528 (registration)
    Registration of the MCP tool 'pylon_get_tag' including name, description, input schema, and thin handler that delegates to PylonClient.getTag.
    server.tool(
    	'pylon_get_tag',
    	'Get a specific tag by ID',
    	{
    		id: z.string().describe('The tag ID'),
    	},
    	async ({ id }) => {
    		const result = await client.getTag(id);
    		return {
    			content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }],
    		};
    	},
    );
  • The handler function for the pylon_get_tag tool, which fetches the tag using PylonClient and returns a formatted text response.
    async ({ id }) => {
    	const result = await client.getTag(id);
    	return {
    		content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }],
    	};
    },
  • Zod input schema for the pylon_get_tag tool requiring a string 'id' parameter.
    {
    	id: z.string().describe('The tag ID'),
    },
  • Core helper method in PylonClient that implements the API call to retrieve a specific tag by ID.
    async getTag(id: string): Promise<SingleResponse<Tag>> {
    	return this.request<SingleResponse<Tag>>('GET', `/tags/${id}`);
    }
  • TypeScript interface defining the structure of a Tag object.
    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 the full burden. It states the action ('Get') but doesn't disclose behavioral traits such as whether this is a read-only operation (implied but not confirmed), error handling (e.g., if the ID doesn't exist), authentication needs, rate limits, or the format of the returned tag data. The description is minimal and lacks essential context for safe invocation.

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 wasted words. It is front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place, achieving optimal conciseness for a simple retrieval operation.

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 simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It lacks details on return values (e.g., what fields the tag object includes), error conditions, or behavioral context needed for reliable use. While minimalism can suffice for very basic tools, this leaves gaps in understanding how to interpret results or handle failures.

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 the 'id' parameter documented as 'The tag ID'. The description adds no additional meaning beyond this, as it only restates 'by ID' without elaborating on format, constraints, or examples. With high schema coverage, the baseline score of 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 'Get a specific tag by ID' clearly states the verb ('Get') and resource ('tag'), with the qualifier 'by ID' specifying the lookup method. It distinguishes from siblings like 'pylon_list_tags' (which retrieves multiple tags) and 'pylon_update_tag' (which modifies tags), but doesn't explicitly contrast with 'pylon_delete_tag' (another ID-based operation).

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. The description implies usage when a specific tag ID is known, but it doesn't mention prerequisites (e.g., needing the ID from another operation), exclusions, or comparisons to siblings like 'pylon_list_tags' for browsing or 'pylon_update_tag' for modifications.

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