Skip to main content
Glama

pylon_delete_tag

Delete a tag by its ID to remove it from the Pylon customer support platform.

Instructions

Delete a tag

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe tag ID to delete

Implementation Reference

  • The handler function for pylon_delete_tag. Takes an id parameter, calls client.deleteTag(id), and returns the result as JSON text content.
    async ({ id }) => {
    	const result = await client.deleteTag(id);
    	return {
    		content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
    	};
    },
  • src/index.ts:1111-1123 (registration)
    Registration of the 'pylon_delete_tag' tool on the MCP server with its description ('Delete a tag'), schema (id: z.string()), and handler callback.
    server.tool(
    	'pylon_delete_tag',
    	'Delete a tag',
    	{
    		id: z.string().describe('The tag ID to delete'),
    	},
    	async ({ id }) => {
    		const result = await client.deleteTag(id);
    		return {
    			content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
    		};
    	},
    );
  • Zod schema for pylon_delete_tag: requires a single 'id' string parameter describing 'The tag ID to delete'.
    {
    	id: z.string().describe('The tag ID to delete'),
    },
  • The PylonClient.deleteTag method sends a DELETE request to /tags/:id and returns a SingleResponse<{ success: boolean }>.
    async deleteTag(id: string): Promise<SingleResponse<{ success: boolean }>> {
    	return this.request<SingleResponse<{ success: boolean }>>(
    		'DELETE',
    		`/tags/${id}`,
    	);
    }
Behavior2/5

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

No annotations provided, so description carries full burden. It only states 'Delete a tag' without disclosing irreversibility, cascading effects, or error conditions. Minimal behavioral insight.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely brief (two words). No wasted language, but the brevity sacrifices explanatory value. For a simple tool, it is acceptable but could include more context without becoming verbose.

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 low complexity (one parameter, no output schema), the description provides the essential action. However, it lacks details on side effects or error handling, making it merely adequate.

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?

Input schema describes the single parameter 'id' as the tag ID to delete, achieving 100% coverage. The description adds no additional semantics, so baseline 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?

Description clearly states verb ('Delete') and resource ('a tag'). Distinguishes from sibling tools like pylon_create_tag and pylon_update_tag by the action. However, it is minimal and could specify the context or tag type.

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 on when to use deletion versus other tag operations (e.g., update). No prerequisites or context for use, leaving the agent without decision support.

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