Skip to main content
Glama

pylon_create_issue_message

Add messages or replies to support issue conversations to respond to customers, provide updates, or add internal notes for issue tracking.

Instructions

Add a new message/reply to a support issue conversation. Use this to respond to customers, add internal notes, or provide updates on issue progress.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_idYesID of the issue to add message to. Example: "issue_abc123"
contentYesMessage text to send. Can include formatting and links. Examples: "Hi John, I've escalated this to our dev team. You should see a fix by tomorrow.", "**Internal note:** This appears to be related to the server migration last week."

Implementation Reference

  • Handler for 'pylon_create_issue_message' tool - validates required arguments (issue_id and content) and calls pylonClient.createIssueMessage(), returning the created message as JSON
    case 'pylon_create_issue_message': {
      if (!args || !('issue_id' in args) || !('content' in args)) {
        throw new Error('issue_id and content are required');
      }
      const message = await pylonClient.createIssueMessage(args.issue_id as string, args.content as string);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(message, null, 2),
          },
        ],
      };
    }
  • Implementation of createIssueMessage method in PylonClient - makes POST request to /issues/{issueId}/messages endpoint with content payload and returns the created PylonMessage
    async createIssueMessage(issueId: string, content: string): Promise<PylonMessage> {
      const response: AxiosResponse<PylonMessage> = await this.client.post(`/issues/${issueId}/messages`, { content });
      return response.data;
    }
  • Tool schema definition for 'pylon_create_issue_message' - defines the tool name, description, and inputSchema with required parameters (issue_id and content)
    {
      name: 'pylon_create_issue_message',
      description: 'Add a new message/reply to a support issue conversation. Use this to respond to customers, add internal notes, or provide updates on issue progress.',
      inputSchema: {
        type: 'object',
        properties: {
          issue_id: { type: 'string', description: 'ID of the issue to add message to. Example: "issue_abc123"' },
          content: { type: 'string', description: 'Message text to send. Can include formatting and links. Examples: "Hi John, I\'ve escalated this to our dev team. You should see a fix by tomorrow.", "**Internal note:** This appears to be related to the server migration last week."' },
        },
        required: ['issue_id', 'content'],
      },
    },
  • Type definition for PylonMessage interface - defines the structure of message objects returned by createIssueMessage (id, content, author_id, issue_id, created_at)
    export interface PylonMessage {
      id: string;
      content: string;
      author_id: string;
      issue_id: string;
      created_at: string;
    }

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/marcinwyszynski/pylon-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server