Skip to main content
Glama
launchnotes

LaunchNotes MCP Server

Official
by launchnotes

Search LaunchNotes Feedback

launchnotes_search_feedback
Read-onlyIdempotent

Search and filter customer feedback in LaunchNotes projects by content, sentiment, importance, and status to analyze user input.

Instructions

Search and filter customer feedback in a LaunchNotes project.

Args:

  • project_id (string): The ID of the project (required)

  • query (string, optional): Search term to find in feedback content

  • reaction ('happy' | 'meh' | 'sad', optional): Filter by customer sentiment

  • importance ('low' | 'medium' | 'high', optional): Filter by importance level

  • organized_state (string, optional): Filter by state ('organized', 'unorganized', 'announcement', 'idea', 'roadmap')

  • starred (boolean, optional): Filter by starred status

  • archived (boolean, optional): Filter by archived status

  • limit (number, optional): Number to return (max 100, default: 20)

  • response_format ('json' | 'markdown'): Output format (default: 'markdown')

Returns: List of feedback items with content, sentiment, importance, customer info, and timestamps

Use Cases:

  • "What are customers saying about Digests?"

  • "Show me all unhappy feedback"

  • "Find high importance feedback that's unorganized"

  • "Search feedback containing 'API integration'"

  • "Show me starred feedback"

Error Handling:

  • Returns "Project not found" if project ID doesn't exist

  • Returns "Authentication failed" if API token is invalid

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesThe ID of the LaunchNotes project
queryNoSearch term to find in feedback content
reactionNoFilter by customer reaction/sentiment
importanceNoFilter by importance level
organized_stateNoFilter by organized state: 'organized', 'unorganized', 'announcement', 'idea', 'roadmap'
starredNoFilter by starred status
archivedNoFilter by archived status
limitNoNumber of feedback items to return (max 100)
response_formatNoOutput format: 'json' for structured data, 'markdown' for human-readablemarkdown

Implementation Reference

  • The asynchronous handler function that implements the core logic of the 'launchnotes_search_feedback' tool. It performs the GraphQL search query via searchFeedback, processes the results, and returns formatted JSON or Markdown output based on parameters. Handles errors gracefully.
    async (params: SearchFeedbackInput) => {
      try {
        const result = await searchFeedback(client, {
          projectId: params.project_id,
          query: params.query,
          reaction: params.reaction,
          importance: params.importance,
          organizedState: params.organized_state,
          starred: params.starred,
          archived: params.archived,
          first: params.limit,
        });
    
        const feedbacks = result.project.feedbacks.nodes;
    
        if (params.response_format === RESPONSE_FORMAT.JSON) {
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(
                  {
                    total: feedbacks.length,
                    feedbacks,
                    hasMore: result.project.feedbacks.pageInfo.hasNextPage,
                  },
                  null,
                  2
                ),
              },
            ],
          };
        }
    
        // Markdown format
        return {
          content: [
            {
              type: "text",
              text: formatFeedbackListMarkdown(feedbacks),
            },
          ],
        };
      } catch (error) {
        return {
          isError: true,
          content: [
            {
              type: "text",
              text: `Error searching feedback: ${error instanceof Error ? error.message : "Unknown error"}`,
            },
          ],
        };
      }
    }
  • Zod schema defining the input parameters and validation for the 'launchnotes_search_feedback' tool, including project_id, filters like query, reaction, importance, and output format.
    export const SearchFeedbackSchema = z
      .object({
        project_id: z
          .string()
          .min(1, "Project ID is required")
          .describe("The ID of the LaunchNotes project"),
        query: z
          .string()
          .optional()
          .describe("Search term to find in feedback content"),
        reaction: reactionSchema,
        importance: importanceSchema,
        organized_state: z
          .string()
          .optional()
          .describe("Filter by organized state: 'organized', 'unorganized', 'announcement', 'idea', 'roadmap'"),
        starred: z
          .boolean()
          .optional()
          .describe("Filter by starred status"),
        archived: z
          .boolean()
          .optional()
          .describe("Filter by archived status"),
        limit: z
          .number()
          .min(1)
          .max(100)
          .default(20)
          .optional()
          .describe("Number of feedback items to return (max 100)"),
        response_format: responseFormatSchema,
      })
      .strict();
  • The server.registerTool call that registers the 'launchnotes_search_feedback' tool, including its name, title, detailed description, input schema reference, and annotations.
        "launchnotes_search_feedback",
        {
          title: "Search LaunchNotes Feedback",
          description: `Search and filter customer feedback in a LaunchNotes project.
    
    Args:
      - project_id (string): The ID of the project (required)
      - query (string, optional): Search term to find in feedback content
      - reaction ('happy' | 'meh' | 'sad', optional): Filter by customer sentiment
      - importance ('low' | 'medium' | 'high', optional): Filter by importance level
      - organized_state (string, optional): Filter by state ('organized', 'unorganized', 'announcement', 'idea', 'roadmap')
      - starred (boolean, optional): Filter by starred status
      - archived (boolean, optional): Filter by archived status
      - limit (number, optional): Number to return (max 100, default: 20)
      - response_format ('json' | 'markdown'): Output format (default: 'markdown')
    
    Returns:
      List of feedback items with content, sentiment, importance, customer info, and timestamps
    
    Use Cases:
      - "What are customers saying about Digests?"
      - "Show me all unhappy feedback"
      - "Find high importance feedback that's unorganized"
      - "Search feedback containing 'API integration'"
      - "Show me starred feedback"
    
    Error Handling:
      - Returns "Project not found" if project ID doesn't exist
      - Returns "Authentication failed" if API token is invalid`,
          inputSchema: SearchFeedbackSchema,
          annotations: {
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: true,
          },
        },
Behavior4/5

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

Annotations already provide key behavioral hints (read-only, open-world, idempotent, non-destructive). The description adds valuable context beyond annotations: it specifies the 'limit' parameter's max (100) and default (20), describes error handling ('Project not found', 'Authentication failed'), and outlines the return format options ('json' vs 'markdown'). This enhances transparency without contradicting annotations.

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?

The description is well-structured with clear sections (Args, Returns, Use Cases, Error Handling) and front-loaded purpose. It's appropriately sized for a tool with 9 parameters, though some redundancy exists between 'Args' and the schema. Every sentence adds value, but it could be more concise by avoiding duplication of schema details.

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?

Given the tool's complexity (9 parameters, no output schema) and rich annotations, the description is mostly complete. It covers purpose, usage examples, error handling, and parameter details. However, without an output schema, it could better describe the structure of returned feedback items (e.g., fields like 'customer info', 'timestamps') to fully compensate for the missing structured output definition.

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 documents all parameters thoroughly. The description's 'Args' section repeats parameter information but adds minimal extra semantics (e.g., clarifying 'organized_state' values). This meets the baseline of 3 since the schema does the heavy lifting, but the description doesn't significantly enhance understanding beyond what's in the schema.

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 tool's purpose: 'Search and filter customer feedback in a LaunchNotes project.' It uses specific verbs ('search', 'filter') and identifies the resource ('customer feedback'), distinguishing it from sibling tools like 'launchnotes_get_feedback' (which likely retrieves specific feedback) and announcement-focused tools.

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 'Use Cases' section provides clear examples of when to use this tool (e.g., 'What are customers saying about Digests?', 'Show me all unhappy feedback'), which implicitly guides usage. However, it doesn't explicitly state when NOT to use it or name alternatives like 'launchnotes_get_feedback' for retrieving specific feedback by ID rather than searching/filtering.

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/launchnotes/mcp'

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