Skip to main content
Glama

pylon_redact_message

Redact a specific message from an issue to remove sensitive or inappropriate content.

Instructions

Redact a message from an issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_idYesThe issue ID
message_idYesThe message ID to redact

Implementation Reference

  • The MCP tool handler for 'pylon_redact_message'. It accepts issue_id and message_id, calls client.redactMessage(), and returns the redacted message as JSON.
    server.tool(
    	'pylon_redact_message',
    	'Redact a message from an issue',
    	{
    		issue_id: z.string().describe('The issue ID'),
    		message_id: z.string().describe('The message ID to redact'),
    	},
    	async ({ issue_id, message_id }) => {
    		const result = await client.redactMessage(issue_id, message_id);
    		return {
    			content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }],
    		};
    	},
    );
  • Input schema for the tool: issue_id (string) and message_id (string) defined using Zod.
    {
    	issue_id: z.string().describe('The issue ID'),
    	message_id: z.string().describe('The message ID to redact'),
    },
  • src/index.ts:1008-1021 (registration)
    Tool registered via server.tool() with name 'pylon_redact_message' and description 'Redact a message from an issue'.
    server.tool(
    	'pylon_redact_message',
    	'Redact a message from an issue',
    	{
    		issue_id: z.string().describe('The issue ID'),
    		message_id: z.string().describe('The message ID to redact'),
    	},
    	async ({ issue_id, message_id }) => {
    		const result = await client.redactMessage(issue_id, message_id);
    		return {
    			content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }],
    		};
    	},
    );
  • The PylonClient.redactMessage() method that sends a POST request to /issues/{issueId}/messages/{messageId}/redact and returns a SingleResponse<Message>.
    async redactMessage(
    	issueId: string,
    	messageId: string,
    ): Promise<SingleResponse<Message>> {
    	return this.request<SingleResponse<Message>>(
    		'POST',
    		`/issues/${issueId}/messages/${messageId}/redact`,
    	);
    }
  • The SingleResponse<T> generic interface used as the response type for redactMessage.
    export interface SingleResponse<T> {
    	data: T;
    	request_id: string;
    }
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits beyond 'redact'. It is unclear if redaction is reversible, if it affects other users, or what permissions are required.

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

Conciseness3/5

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

The description is very short (7 words), which is concise but at the expense of useful detail. It front-loads the action and resource, but lacks structure for additional guidance.

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 absence of annotations and output schema, the description is incomplete. It does not explain return values, side effects, or when redaction is appropriate, leaving the agent with insufficient context.

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% with basic descriptions for issue_id and message_id. The description adds no additional meaning beyond the schema, meeting the baseline.

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 (redact) and the resource (a message from an issue). It distinguishes from sibling tools like pylon_delete_issue by using a different verb, but does not elaborate on what redaction entails.

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 this tool vs alternatives such as pylon_delete_issue or pylon_update_issue. No when-not or prerequisite information.

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