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;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it implies a write operation ('Add'), it doesn't disclose important traits like authentication requirements, rate limits, whether messages are editable/deletable, or how the system handles different message types (customer vs internal). The description mentions message purposes but lacks operational details.

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?

Two efficient sentences that front-load the core purpose and follow with usage contexts. Every word earns its place with no redundancy or unnecessary elaboration. The structure moves from general action to specific applications.

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?

For a write operation with no annotations and no output schema, the description is adequate but incomplete. It covers the what and why well, but lacks information about behavioral consequences, error conditions, or response format. Given the mutation nature and absence of structured safety hints, more disclosure would be beneficial.

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%, so the schema already fully documents both parameters. The description adds no additional parameter information beyond what's in the schema. This meets the baseline of 3 when schema coverage is high, but doesn't provide extra value like format examples or constraints.

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 the specific action ('Add a new message/reply') and target resource ('to a support issue conversation'), distinguishing it from siblings like pylon_create_issue (creates issues) and pylon_get_issue_messages (reads messages). It goes beyond the tool name by specifying the conversational context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool ('to respond to customers, add internal notes, or provide updates on issue progress'), giving practical examples. However, it doesn't explicitly state when NOT to use it or mention alternatives like pylon_update_issue for other issue 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/marcinwyszynski/pylon-mcp'

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