Skip to main content
Glama

pylon_get_tag

Retrieve a specific tag by its ID from the Pylon customer support platform.

Instructions

Get a specific tag by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe tag ID

Implementation Reference

  • The handler function for pylon_get_tag. It calls client.getTag(id) and returns the result as JSON.
    async ({ id }) => {
    	const result = await client.getTag(id);
    	return {
    		content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }],
    	};
    },
  • The input schema for pylon_get_tag, which requires only an 'id' string parameter describing the tag ID.
    {
    	id: z.string().describe('The tag ID'),
    },
  • src/index.ts:1060-1072 (registration)
    Registration of the 'pylon_get_tag' tool via server.tool() with name, description, schema, and handler.
    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 client.getTag() helper method that sends a GET request to /tags/{id} to fetch a tag by its ID.
    async getTag(id: string): Promise<SingleResponse<Tag>> {
    	return this.request<SingleResponse<Tag>>('GET', `/tags/${id}`);
    }
  • The Tag interface definition describing the shape of a tag object (id, value, object_type, optional hex_color).
    export interface Tag {
    	id: string;
    	value: string;
    	object_type: 'account' | 'issue' | 'contact';
    	hex_color?: string;
    }
Behavior4/5

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

No annotations exist, so the description carries full burden. It clearly indicates a read operation with no side effects, which is accurate. However, it does not mention permissions or rate limits, which are not critical for this simple 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?

A single sentence with no fluff. It is front-loaded and provides the essential information efficiently.

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

Completeness4/5

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

For a simple one-parameter get operation, the description is mostly complete. It could optionally mention the return type (tag object), but the lack of output schema and the simplicity of the action make this acceptable.

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 coverage is 100% and the parameter description in the schema ('The tag ID') is sufficient. The description adds 'by ID' which reinforces but does not add new meaning beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

The description clearly states it retrieves a specific tag by ID, using a specific verb and resource. It distinguishes from list_tags (which returns all) and create_tag.

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 when you have a specific ID, but does not explicitly state when to use this tool over alternatives like list_tags or search_tags. No exclusions or context 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