Skip to main content
Glama
carlosazaustre

Activity Reporting MCP Server

submit_product_feedback

Submit a product feedback activity draft to the Activity Reporting MCP Server. Capture details like title, description, activity date, product details, and time spent for efficient reporting.

Instructions

Submit a product feedback activity draft

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activityDateYesParticipation Date (YYYY-MM-DD format)
additionalInfoNoAdditional information (optional)
contentTypeYesContent type
descriptionYesDescription
metricsYes
privateNoDo you want to make this activity private? (optional)
productDescriptionYesWhat product was it about?
tagsNoTags (optional)
titleYesTitle

Implementation Reference

  • src/server.ts:362-423 (registration)
    Registration of the 'submit_product_feedback' tool in the ListToolsRequestSchema handler, including detailed input schema definition.
    {
      name: "submit_product_feedback",
      description: "Submit a product feedback activity draft",
      inputSchema: {
        type: "object",
        properties: {
          title: {
            type: "string",
            description: "Title",
            minLength: 3,
            maxLength: 200,
          },
          description: {
            type: "string",
            description: "Description",
            maxLength: 2000,
          },
          activityDate: {
            type: "string",
            pattern: "^\\d{4}-\\d{2}-\\d{2}$",
            description: "Participation Date (YYYY-MM-DD format)",
          },
          contentType: {
            type: "string",
            enum: Object.values(ProductFeedbackContentType),
            description: "Content type",
          },
          productDescription: {
            type: "string",
            maxLength: 500,
            description: "What product was it about?",
          },
          tags: {
            type: "array",
            items: { type: "string" },
            description: "Tags (optional)",
            minItems: 0,
          },
          metrics: {
            type: "object",
            properties: {
              timeSpent: {
                type: "integer",
                minimum: 1,
                description: "Time spent (in minutes)",
              },
            },
            required: ["timeSpent"],
          },
          additionalInfo: {
            type: "string",
            maxLength: 2000,
            description: "Additional information (optional)",
          },
          private: {
            type: "boolean",
            description: "Do you want to make this activity private? (optional)",
          },
        },
        required: ["title", "description", "activityDate", "contentType", "productDescription", "metrics"],
      },
    },
  • Handler dispatch in the CallToolRequestSchema switch statement, mapping the tool call to the shared submitActivityDraft method with specific endpoint 'product-feedback-given'.
    case "submit_product_feedback":
      return await this.submitActivityDraft("product-feedback-given", args as unknown as ProductFeedbackDraft);
  • Shared helper function that executes the core logic: POSTs the product feedback draft to the 'product-feedback-given' endpoint on the Advocu GDE API, handles responses and errors.
    private async submitActivityDraft(
      endpoint: string,
      data:
        | ContentCreationDraft
        | PublicSpeakingDraft
        | WorkshopDraft
        | MentoringDraft
        | ProductFeedbackDraft
        | GooglerInteractionDraft
        | StoryDraft,
    ): Promise<{
      content: Array<{
        type: string;
        text: string;
      }>;
    }> {
      const url = `${this.baseUrl}/activity-drafts/${endpoint}`;
    
      try {
        const response = await fetch(url, {
          method: "POST",
          headers: {
            "Content-Type": "application/json",
            Authorization: `Bearer ${this.accessToken}`,
          },
          body: JSON.stringify(data),
        });
    
        if (!response.ok) {
          const errorText = await response.text();
          let errorMessage = `GDE API error (${response.status})`;
    
          if (response.status === 401) {
            errorMessage = "❌ GDE authentication failed. Your ADVOCU_ACCESS_TOKEN may be expired or invalid.\n\nPlease check your Advocu access token configuration.";
          } else if (response.status === 400) {
            errorMessage = `❌ GDE API rejected the request:\n\n${errorText}\n\nPlease check:\n- All required fields are present\n- Field values match expected formats\n- Tags are valid\n- Date format is correct (YYYY-MM-DD)`;
          } else if (response.status === 429) {
            errorMessage = "⏱️ GDE API rate limit exceeded (30 requests/minute). Please wait and try again.";
          } else {
            errorMessage = `❌ GDE API error (${response.status}):\n\n${errorText}`;
          }
    
          // Return error as content instead of throwing
          return {
            content: [
              {
                type: "text",
                text: errorMessage,
              },
            ],
          };
        }
    
        const result = (await response.json()) as Record<string, unknown>;
    
        return {
          content: [
            {
              type: "text",
              text: `✅ GDE Activity draft submitted successfully!\n\nEndpoint: ${endpoint}\nStatus: ${response.status}\nResponse: ${JSON.stringify(result, null, 2)}`,
            },
          ],
        };
      } catch (error) {
        if (error instanceof McpError) {
          throw error;
        }
        const errorMsg = this.getErrorMessage(error);
        throw new McpError(
          ErrorCode.InternalError,
          `❌ Failed to submit GDE activity:\n\n${errorMsg}\n\nEndpoint: ${endpoint}`
        );
      }
    }
  • Type definition for ProductFeedbackDraft, providing structure and validation types for the tool's input parameters.
    export interface ProductFeedbackDraft extends ActivityDraftBase {
      /** Type of product feedback content */
      contentType: ProductFeedbackContentType;
      /** Description of what product the feedback was about */
      productDescription: string;
      /** Metrics related to time investment */
      metrics: {
        /** Time spent providing feedback (in minutes) */
        timeSpent: number;
      };
    }
  • Enum defining valid values for the 'contentType' field in the product feedback tool schema.
    export enum ProductFeedbackContentType {
      EARLY_ACCESS_PROGRAM = "Early access program",
      PRODUCT_FEEDBACK_SESSION = "Product feedback session",
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Submit a product feedback activity draft' implies a write operation, but it doesn't specify whether this creates a new record, updates an existing one, requires authentication, has side effects, or what happens upon submission. For a mutation tool with zero annotation coverage, this is inadequate.

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?

The description is a single, efficient sentence with zero waste—it directly states the tool's action and resource. It's appropriately sized and front-loaded, making it easy to parse quickly without unnecessary elaboration.

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 tool's complexity (9 parameters, nested objects, no output schema) and lack of annotations, the description is incomplete. It doesn't address behavioral aspects like mutation effects, error handling, or return values, which are critical for a submission tool. With no output schema and minimal description, the agent lacks sufficient context for reliable use.

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 high at 89%, so the schema already documents most parameters well. The description adds no additional meaning beyond the schema, such as explaining relationships between parameters or usage examples. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but doesn't need to heavily.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action ('submit') and resource ('product feedback activity draft'), which clarifies the basic purpose. However, it doesn't differentiate this tool from sibling tools like submit_content_creation or submit_story, which likely handle different types of activities. The purpose is clear but lacks sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context (e.g., for product-related feedback vs. other activities), or exclusions. With sibling tools like submit_mentoring and submit_workshop available, this gap leaves the agent uncertain about tool selection.

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

Related 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/carlosazaustre/advocu-mcp-server'

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